I created a Azure VM in DevTestLab using base Windows Server 2016 DataCenter. Then I enabled web server role referencing this.
It seems there is some issue with IIS 10 as I am not able to access default website on this server. To verify further, I also tried to host a website with single html page but same issue "Page can't be displayed."
I gave a try with chrome browser and able to browse localhost website on chrome. So IIS 10 seems good on VM. Initially I guess was IIS 10 not configured properly but now it seems proxy on IE not allowing website content getting displayed. Now I am able to proceed with chrome and will reach out our network team if required.
Related
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 setup a SharePoint 2019 high-availability farm with 2 WFE's, 2 APP and 2 SQL Servers. All servers state is good and patched the farm with May 2022 Cumulative Update. We are running F5 load balancer and public IP of the load balancer (LB) is also added in the host file of both WFE servers.
We created a web application (its public facing site, so also added anonymous authentication) and added DNS to it. We have setup the AAM in central Admin and also added IIS binding for web application port and 443 (wildcard certificate is installed on both WFE servers).
When Load Balancer is pointed to WFE1, the application is loading perfectly fine, however when LB is pointed to WFE2, its showing a blank white page (with no JS or CSS loaded on the page, no errors). However, when we do IISRESET on WFE2, first time site loads on WFE2 and then goes blank if we refresh the browser or click on any link on the website. The application is working fine with server name on both the servers
We have tested on different browsers. Also added Disableloopbackcheck in Registry. All required firewall rules (ports) are open. Each server is getting pinged from one another, so there is no server communication issue. Even the required SharePoint files/folders are excluded from antivirus (Bitdefender). Also, there is no other web application on this farm which is using SSL/https.
I have also checked SharePoint ULS logs, Event Viewer logs and IIS logs, but it seems there are no errors.
Any help would be highly appreciated!
I have a windows server 2019 VM in Azure.
On this server I have multiple web sites running.
One web site has two URL's
For example https://api.oldcompanyname.com (192.1.1.5) and https://api.newcompanyname.com (192.1.1.6)
I have certificates for both, each has its own binding, and each has its own IP address.
Locally on the machine I can access both sites with no issue.
However remotely the old site URL pulls up just fine, but the new site URL gives me a 503 error.
I have checked the IIS logs and I don't see any of the 503 errors listed in there.
I checked the windows logs and there are no crashes with the AppPool and again running locally (with FQDN) works just fine so the site is loading.
Windows firewall is turned off.
In Azure we do have this server behind a Traffic Manager, PF Sense, and App Gateway.
I want to rule out any issues on this server before I go searching in one of these areas
Funny thing is that even from another machine inside the network I get the 503 on this one binding and I don't think that that connection would go through any of above items as it is an internal address it is using.
Any ideas?
I developed a web app, published it to the File System and try to setup the IIS to make it available to a Virtual Machine with XP and a IE8.
Everything is fine in my computer, I can see the website, but from the VM I can't and it's because the setting "Enable remote connections" in the management tab in the Site in the IIS is not checked.
The problem is that option (view image)Manage does not appear under my Site in the IIS.
I already added all the features related with this but nothing works.
It is a asp.net application.
Any guesses?
Thanks
Solved it,
The Network Address Translation option they give in the setting will work.
Just need to access the address that both machines are using for the bridge, so you will have to go to look at the network configuration
I configured the Default website in IIS for SSL by creating a CSR using the IIS itself, submitted it to a CA, and assigned the issued certificate as the server certificate. That's all is required in this world to setup server SSL. But when I open the https url it says "Internet Explorer cannot display the webpage". Which pillar should I bang my head against to get it working? The only help from microsoft I could find is that useless arcicle http://support.microsoft.com/?id=290391 that presupposes you are configuring a non-default website for SSL and goes on and on about port conflict. I'm using default website for https.
I'm using windows xp, IIS 5.1 and Microsoft Management Console 3.0.
Please help or courier me a shotgun for shooting myself.
Edit: After I configured IIS for SSL, the Apache Tomcat server which had been configured on port 8080 has suddenly stopped working. The 8080 urls just timeout. What is the connection?
Edit: Because I can't live without Tomcat on my machine, I used another machine to setup IIS SSL after stopping the tomcat there. I face the same problem there, "Internet Explorer cannot display the webpage". Please help before I shoot myself.
Don't shoot!
XP has given me fits with SSL... have you tried setting the application pool to high/isolated setting up the website with an identity under COM?
That seemed to solve some issues for me.
Also - did you make sure to set it up in the correct stores? Is this an application that is running under your account or a service account? If it is a service account you may need to do a RUN AS on the certificate management console and add under that user's personal store as well as under the appropriate store for the machine/computer.
Good luck.