Recently there was a new deployment to my website. In web server, on click of browse website option in IIS using localhost, website is working fine but with a certificate error in the browser.
Problem : When trying to access the URL from client browser, I'm getting 503 communication error! What might be reason?
Need a quick resolution as the site is down :(
Enabled Directory Browsing in IIS & problem is resolved!
Related
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 have been facing a very weird issue with a simple web application that I have recently deployed using IIS. This is an already working application in a server in NA region. I re-created the same exact IIS environment in a new server from a different region. When I try to login using the new URL, I get the following error message.
I have double-checked multiple times that my IIS configuration is exactly same as my old (working) server.
Here is what I have selected for the Authentication setting of the server.
Kindly help with the pointers. Thank you.
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?
If I create a small web api project and publish it to a server with IIS7.5, i can't open the site. I get an
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Someone who can help?
Does your site have a default page? Try putting the address to the default page in the URL.
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.