You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2018. It is now read-only.
Deployed ASP.NET MVC Core 1.1.1 on Windows 2012 Server R2. Followed this ASP.NET article (installed DotNetCore.1.0.5_1.1.2-WindowsHosting bundle etc). App runs fine as localhost on the server if we follow the following steps:
In cmd from root dir of the app, ran: dotnet MyWebapplication.dll
Noticed that application is running and waiting for responses on localhost:5000.
Opened the browser on the host server and navigated to: http://localhost:5000
Home page opened as expected
But when we navigate to the http://IP Address/MyWebapplication on a different desktop on the same network, we get the 500 - Internal Server Error
NOTE: We tested that if we host a simple web app (not ASP.NET Core) with just one Index.html page on IIS, we can access the app from another machine on the same network via, say, http://IP Address/MySimpleHtmlApp. So issue seems to be related to something on ASP.NET Core deployment on IIS. Question: What we may be missing and how to resolve it?
The text was updated successfully, but these errors were encountered:
Resolved. The issue was that although I had installed DotNetCore.1.0.5_1.1.2-WindowsHosting bundle but the ASPNETCore was not showing up in IIS->Modules. So, I uninstalled the bundle and the restarted the machine, installed the bundle again, restarted the machine (as precaution).
Deployed ASP.NET MVC
Core 1.1.1
onWindows 2012 Server R2
. Followed this ASP.NET article (installed DotNetCore.1.0.5_1.1.2-WindowsHosting bundle etc). App runs fine as localhost on the server if we follow the following steps:http://localhost:5000
But when we navigate to the
http://IP Address/MyWebapplication
on a different desktop on the same network, we get the500 - Internal Server Error
NOTE: We tested that if we host a simple web app (not ASP.NET Core) with just one Index.html page on IIS, we can access the app from another machine on the same network via, say,
http://IP Address/MySimpleHtmlApp
. So issue seems to be related to something on ASP.NET Core deployment on IIS. Question: What we may be missing and how to resolve it?The text was updated successfully, but these errors were encountered: