-
Notifications
You must be signed in to change notification settings - Fork 524
Server fails to start with "error -97 EAFNOSUPPORT address family not supported" #1474
Comments
I tried out your image on Debian 8.2 and don't see the EAFNOSUPPORT. The results of my experiment can be seen in this gist. Have you tried changing your binding from http://*:80 to http://0.0.0.0:80? That seems to have fixed the problem for the reporter of #766. |
Thanks, that resolved the problem. Didn't think about IPV6 :-) Thank you! |
Reopenning for triaging. I think we could do what I suggested in this comment, and try binding to If we remove or change |
Is I used the default option (not using |
The default binding is normally We currently handle not being able to bind to Previously we weren't able to reproduce the EAFNOSUPPORT issue though. @MarkusAmshove can you provide us with the exact host and guest distro versions you were using when you ran into this issue? |
I'm using a QNAP TS-251+ (it's a NAS). Host
It does support IPV6, but I haven't enabled it. GuestThe guest is using
which uses microsoft/dotnet:1.1.1-runtime itself. Tracking down the Dockerfiles it is Windows 10I can't reproduce it on Windows by simply disabling IPv6:
trying to force disable IPv6 by using
|
Assigning to @halter73 for investigation. |
I just started having this occur in our Azure App Service a few days back. We're using AspNetCore 2.1.4. |
@zmk523 Can you show us your logs? The EAFNOSUPPORT binding issue should be benign on azure and should only be logged as a warning. Are you seeing any other problems with your app, or just this log? |
Also, can you share which version of ASP.NET Core you are using? This is listed as a PackageReference element in your .csproj file. You said ASP.NET Core 2.1.4, but there is no such thing. I'm guessing the "2.1.4" is the SDK version, but the SDK can be used to build and app with Kestrel 1.0, 1.1, 2.0, etc. |
@natemcmaster |
@halter73 Unhandled Exception: Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvException: Error -4092 EACCES permission denied |
EACCES is a different error. This typically means the port you tried to bind to is already in use, or that the port is reserved by the system. Can you open a separate bug for this? This issue was about EAFNOSUPPORT |
@natemcmaster |
Hello,
I'm using the ASP.NET Core project template from Visual Studio 2017 and built it with docker, pushed it to the registry and then pulled it on my QNAP NAS.
When trying to start the container I get the following stacktrace:
I did not change anything on the project itself, so it's just built as is (from the template).
I've tried all 3 network modes (Bridge, NAT, Host) but I always get the same error.
Searching for the error just points me to issues which were closed without any hint on what goes wrong .
The image is hosted at dockerhub:
https://hub.docker.com/r/markusamshove/musikgeschaeft/
The text was updated successfully, but these errors were encountered: