Hosted a .NET 6 basic Web App in IIS Web Server inside the Azure Virtual Machine (Windows 2016 Data Center)
Commands:
dotnet new webapp
dotnet run
dotnet publish -c Release
3rd command is used for placing release folder files in the Site Physical Path created in IIS Web Server:
It shown the result as welcome page. After VM Stop and Start action, it is showing the localhost as "The Site can't be reached"
If I create new site on Connections of the IIS Manager, then it is working.
Every time after restarting the VM, Creating New Site is not the solution.
Why previously created Site is showing me "The Site can't be reached" error.
What I have tried:
Tested by creating new Site in Connections of the IIS Manager, it worked for the new site but after restarting the VM, it also stopped working and showing above mentioned error.
Checked VM Status, it is Healthy
All required tools are installed in the VM (VS Code, .NET 6 SDK, Runtime, and Hosting Bundle)
Note: It is working successfully after I clear the cache in the browser after server restart (stop and start) but why I have to clear the browser cache every time after VM stop and start?
Update:
Forgot to mention this:
I have given HTTPS binding to the IIS Manager Website Hosted so if do localhost with port 80, it will shows IIS Web Served Home Page and localhost with Https (443), it will show the hosted website content.
After Server Stop and Start, localhost with port 80 gives the IIS Web Served Home Page and localhost with Https is not giving the website content, here it is giving error "The site is not reached".
Fix:
I have found the fix to this issue which is:
Hosting works with particular time period.
Every time when you launch the Website hosted in VM through IIS Web Server after Server restart (several hours), you need to re-host or create new site in IIS Manager Pool.
I tried to reproduce the same in my environment and I got the results like below:
I have created sample website and when I tried Stop and Start action, localhost reached successfully:
As suggested by samwu you can check event viewer like below:
In start -> select event viewer -> click Windows Logs node
Select application Event Log and Search for errors associated with the failing app like below
You can make use of Debug Diagnostics tool.
I have a problem where a site runs okay on hosting server browser but not on my local browser.
It is a site I need to migrate from a windows 2012 server to a new windows 2019 server. I have ensured all IIS components are setup on the new Windows 2019 server. I copied over all files and re-created the site in IIS on new server with, as far as I can see, exactly the same IIS configurations except the Connection string is set to database on new server which was also migrated from old server. I have checked the websites root folder permissions are the same too
The site is built in ASP.NET and both ASP.NET authentication and windows authentication are enabled and anonymous authentication is disabled. The application pools' "identity" is set to "ApplicationPoolIdentity" as was the old site.
To ensure the site worked on new server I created a registry entry for "DisableLoopbackCheck" because the site continually asked for credentials and with registry change my credentials were accepted and site appeared
Lastly, I have asked ICT to ensure the local DNS is set to new site and the old site in old server is stopped. However I still continue to receive "HTTP Error 404. Resource not found" in both Edge and Chrome. I have also viewed the IIS logs for site but tell me very little
Why do I keep getting this 404 error please? I feel it is something simple I am missing
I am trying to host a Node.JS app on a server that also has IIS running on it. I can open the site in the server browser. As you can see i have the website iisnode running in the browser and it is added in the IIS manager
However, i can not access this site from a different computer using ServerURL/siteName. I just get this error:
What could i be doing wrong? It works locally so i must be close to having it working. I can access other sites hosted on this server so i know the issue is with this app specifically.
We have a .net web application running on iis 8 using windows authentication.
Everything was working fine until we installed a new version of our application without any changes to the iis settings or in the apps web.config file.
The problem is that ever since when we try to open up the app in a browser and fill out the windows authentication popup with valid user user information, it just wont authenticate and after the third try we get a 401.1 error message. This happens when we try to access the website from any pc even the pc that hosts iis and even when we try to launch the site through iis.
Any ideas on what could cause such a thing?
I am using windows server 2012 R2. After installing IIS. my website page still shows remote web access is turned off please tell me how to turn it on.