none
Unable to bind to http://localhost:5000 on the IPv6 loopback interface: RRS feed

  • Question

  • I cloned this .net core app and tried to run it using dotnet run and I get the the error. The app runs in VS 2019 iis express.

    warn: Microsoft.AspNetCore.Server.Kestrel[0]
          Unable to bind to http://localhost:5000 on the IPv4 loopback interface: 'An attempt was made to access a socket in a way forbidden by its access permissions.'.
    warn: Microsoft.AspNetCore.Server.Kestrel[0]
          Unable to bind to http://localhost:5000 on the IPv6 loopback interface: 'An attempt was made to access a socket in a way forbidden by its access permissions.'.
    crit: Microsoft.AspNetCore.Server.Kestrel[0]
          Unable to start Kestrel.
    System.IO.IOException: Failed to bind to address http://localhost:5000.
     ---> System.AggregateException: One or more errors occurred. (An attempt was made to access a socket in a way forbidden by its access permissions.) (An attempt was made to access a socket in a way forbidden by its access permissions.)
     ---> System.Net.Sockets.SocketException (10013): An attempt was made to access a socket in a way forbidden by its access permissions.

     

    Thursday, December 26, 2019 2:05 AM

All replies

  • Hi kobosh,

    Thank you for posting here.

    According to your description, your question is more related to docker. You can consider posting it in docker forums for more efficient responses.

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework.

    Thank you for your understanding.

    Best Regards,

    Xingyu Zhao


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, December 26, 2019 6:17 AM
  • Thanks ....I came again today to find  that  I can browse to the website  on local host 5001. It needs to wait for several minutes to load after first showing 

    This site can’t be reached

    The application is not on docker. Docker is clear empty ..nothing in it ..no container ..volume or image..



    • Edited by kobosh Thursday, December 26, 2019 1:48 PM
    Thursday, December 26, 2019 1:25 PM
  • What about this?  I cannot open app in browser local host : 5000 or 5001 . Not sure if it is ging to pop up after long tile..I am running windows 10 pro

    PS C:\users\kokob> dotnet new mvc -o hiko
    The template "ASP.NET Core Web App (Model-View-Controller)" was created successfully.
    This template contains technologies from parties other than Microsoft, see https://aka.ms/aspnetcore/3.1-third-party-notices for details.

    Processing post-creation actions...
    Running 'dotnet restore' on hiko\hiko.csproj...
      Restore completed in 343.33 ms for C:\users\kokob\hiko\hiko.csproj.

    Restore succeeded.


    PS C:\users\kokob> cd hiko
    PS C:\users\kokob\hiko> dotnet run
    warn: Microsoft.AspNetCore.Server.Kestrel[0]
          Unable to bind to http://localhost:5000 on the IPv4 loopback interface: 'An attempt was made to access a socket in a way forbidden by its access permissions.'.
    warn: Microsoft.AspNetCore.Server.Kestrel[0]
          Unable to bind to http://localhost:5000 on the IPv6 loopback interface: 'An attempt was made to access a socket in a way forbidden by its access permissions.'.
    crit: Microsoft.AspNetCore.Server.Kestrel[0]
          Unable to start Kestrel.

    Thursday, December 26, 2019 2:43 PM
  • Hi kobosh,

    If your application is not on docker, I suggest you post your question in ASP.NET Core forum for better help.

    Thank you for your understanding.

    Best Regards,

    Xingyu Zhao


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, December 27, 2019 1:15 AM