Base solution for your next web application
Open Closed

Startup issue with ASP.NET CORE & Angular (single solution) #6432


User avatar
0
BTSDEV created

I have downlaoded the project v6.5.0 for ASP.NET CORE & Angular (single solution), .NET Core 2.2. I made Web.Host project as startup project in Visual Studio. when i run the project, I see console windowcomes up and says listening on "http://localhost:5000". When I try to browse in chrome browser, i get the message "This localhost page can't be found"

Also, similar issue when I try to start the angular project using "npm start" command. When I do that, it compiles all of the angular components succesfully , When I try to browse in the chrome broweser using url "http://localhost:4200". progressbar keeps spinning on the browser and i dont see any modules loaded in the browser. Also, dont see any error on the browser console.

UPDATE: Thank you for the reply. This is happening on the LIVE project download. I dont see any error being logged into the App_Data\Logs\Logs.txt file as well. Everythign seems normal activities there.

INFO [4 ] soft.AspNetCore.Hosting.Internal.WebHost - Request starting HTTP/1.1 GET http://localhost:5000/
INFO [4 ] soft.AspNetCore.Hosting.Internal.WebHost - Request finished in 533.5002ms 404

Appreciate your timely response ont his issue. I am kind of struck at this point.

Thanks, btsDev


7 Answer(s)
  • User Avatar
    0
    taxpacc created

    I have the exact same issue. While I appreciate the complexity of this project, it's a little disappointing to download it immediately after paying for it, and find it won't even start.

    I'm just glad we found this with a demo project, and not with out one live project.

    Please sort this out asap.

  • User Avatar
    0
    taxpacc created

    I should clarify, we litterally made no changes to the project after download, just ran the migrations to create a db. And our host project is running on 22742. I do see messages in the output window from "ASP.NET Core Web Server", which shows...

    ITS.TaxDemo.Web.Host> Hosting environment: Development
    ITS.TaxDemo.Web.Host> Content root path: D:\Source\TaxDemoSingle\TaxDemo\src\ITS.TaxDemo.Web.Host
    ITS.TaxDemo.Web.Host> Now listening on: http://127.0.0.1:1359
    ITS.TaxDemo.Web.Host> Application started. Press Ctrl+C to shut down.
    

    However if you try to go to that port, you get a 400 error.

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi Guys,

    Are you running the project using Visual Studio ? Normally Host project must be runned on 22742 port and Angular project on 4200.

    If Host project is running on a different port, then Angular app can't access it.

    @BTSDEV in your case, can you browse the Host app on http://localhost:22742 ? taxpacc in your case, it seems like host project is running on http://127.0.0.1:1359, can you see the swagger UI when you visit http://127.0.0.1:1359 ?

    If you guys can't solve this problem, please send your TeamViewer ID & Password to info@aspnetzero and we will help you to run it.

    Thanks,

  • User Avatar
    0
    BTSDEV created

    hi, thank you for the reply. I am running my solution on VS Enterprise Version 15.9.5. When I try to browse to.. http://localhost:22742. getting the following error:

    This site can’t be reached localhost refused to connect. Search Google for localhost 22742 ERR_CONNECTION_REFUSED

    I have sent the teamViewer ID & Password to [email protected] email ID.

    Thank you for your time in helping to resolve this issue.

    Thanks, BtsDev.

  • User Avatar
    0
    ismcagdas created
    Support Team

    The problem of BTSDEV solved via TeamViwer connection. The problem was running Host project on 5000 port, we have switched to 22742 and problem solved.

  • User Avatar
    0
    taxpacc created

    Teamview details sent to info email address. Looking forward to connecting.

  • User Avatar
    0
    ismcagdas created
    Support Team

    Helped via TeamViwer. There were no issue but we need to add more details about merged solution into our documentation.