CODEWITHSUNDEEP
c#kestrel-http-server
Ping Pong
Ping Pong

Reputation: 139

Kestrel unable to start

When specifying a port to bind to with .UseKestrel() I get the errors listed below.. but if I remove the kestrel options everything works normally if I check the API from my browser.

I've tried binding to the port that my application defaults to with no ports chosen and I've tried checking netstat to actively avoid any ports that are in use. Nothing works but removing the options entirely. This is not replicated on my Mac or another Windows 10 machine. This device is Windows 10. 

.UseKestrel(options =>
{
    options.Listen(IPAddress.Loopback, 50470);
    options.Listen(IPAddress.Any, 80);
})

: Microsoft.AspNetCore.Server.Kestrel[0]
Overriding address(es) 'http://localhost:50470/'. Binding to endpoints defined 
in UseKestrel() instead.
crit: Microsoft.AspNetCore.Server.Kestrel[0]
Unable to start Kestrel.
System.Net.Sockets.SocketException (10013): An attempt was made to access a 
socket in a way forbidden by its access permissions
at 
System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException
(SocketError error, String callerName)
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress 
socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransport.
BindAsync() at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer. 
<>c__DisplayClass21_01.<<StartAsync>g__OnBind|0>d.MoveNext() `

Upvotes: 12

Views: 24100

Answers (7)

hrishi rane
hrishi rane

Reputation: 1

Try Updating The Https Certificate with this command. It worked for me!!

dotnet dev-certs https

Upvotes: 0

AminRostami
AminRostami

Reputation: 2772

When you run an ASP.NET Core application directly through Kestrel, without an additional reverse proxy like IIS or nginx, you will need to configure the hosting URL properly.

The problem was because, you did not follow Port sharing limitation in Kestrel web server.

When you to use the Kestrel web server, you should set unique port to app. (if you use the port 80, make sure no apps use this port). and your app has enough permissions, too.

more info:

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-2.2

I hope is useful.

Upvotes: 1

Andy
Andy

Reputation: 43

The additional binding of port 80 in ".UseKestrel(options => { options.Listen(...) })" was causing the issue in my case.

Upvotes: 1

Mr. Kone
Mr. Kone

Reputation: 39

In my case, Removing invalid local IP and Port address combinations from the app's launchSettings.json did it.

Upvotes: 2

Omid Rahimi
Omid Rahimi

Reputation: 477

After Windows Update, some ports are reserved by Windows and applications cannot bind to these ports. please check this command for forbiden port on Os

netsh interface ipv4 show excludedportrange protocol=tcp

Upvotes: 6

norgie
norgie

Reputation: 517

Also check Darkthread's answer here: https://superuser.com/questions/1486417/unable-to-start-kestrel-getting-an-attempt-was-made-to-access-a-socket-in-a-way

We discovered that a port we had been using for a long time wasn't acccessible anymore because it had been reserved by Windows! You may wish to check reserved ports using this command: netsh interface ipv4 show excludedportrange protocol=tcp

Upvotes: 28

Ping Pong
Ping Pong

Reputation: 139

The problem was with the additional binding of port 80, updating this corrected the problem.

Upvotes: -1

Related Questions