I sometimes have a problem after a server reboot one of the sites in IIS does not working.
When browsing Internet Explorer immediately displays 'Navigation to the webpage was cancelled'.
I don't see any errors in the IIS file logs (although I forgot to check the event viewer, and currently do not have access to the server).
The site says it is started, and checking with netstat says the System process has the port allocated. Restart doesn't help.
What does help however is stopping the site, changing the port, starting the site, stopping the site, changing the port back to the original value and finally starting the site. So it seems unlikely there is a port conflict.
Any help would be greatly appreciated, thanks.
I got access to the event viewer after all and saw some warnings concerning SSL. There was also an SChannel error.
It will probably be a problem with the certificate, as described in this article
http://www.iis.net/learn/troubleshoot/security-issues/troubleshooting-ssl-related-issues-server-certificate
If I can reproduce, I will try to follow these steps.
Related
This problem has a very simple (almost silly) fix, but it took me 2 hours to discover today, and none of my searches gave the answer, so I am posting this along with the answer to help others.
I have a website set up in IIS to run locally, which has worked in the past.
The URL is like: http://localhost/mywebsite
But today when I tried to open the site, it did not work in any of my browsers (IE, Chrome, and Firefox).
Even the main IIS Welcome page at http://localhost was not working.
Internet Explorer showed: "Can't reach this page / Make sure the web
address http://localhost is correct". Under "More information", it
showed "There was a temporary DNS error. Try refreshing the page.
Error Code: INET_E_RESOURCE_NOT_FOUND"
Firefox showed: "Unable to connect / Firefox can't establish a
connection to the server at localhost."
Chrome showed: "This site
can't be reached / localhost refused to connect /
ERR_CONNECTION_REFUSED"
Neither restarting the server in IIS, nor calling iisreset from a command prompt fixed it.
I compared my "hosts" file to another computer which was not having the problem. Both had the same entry for "127.0.0.1 localhost".
I checked the Services panel and verified that "World Wide Web Publishing Services" was running.
I ran "netstat -a". It showed nothing listening on port 80, but I didn't know what was causing that.
Based on suggestions I found while searching for a solution, I tried the following, none of which fixed the problem:
I turned off User Account Control.
In IIS, I updated the Site Bindings for "Default Web Site" to change the port number from 80 to a different value, 8085. The site did not load with the new port number either.
In case something in IIS had gotten corrupted or messed up, I used "Turn Windows features on or off" to turn off all the features for Internet Information Services.
Then after rebooting, I turned them all on again and rebooted again.
I still had the same problem.
What else could be causing IIS and my local website not to work?
Make sure the website has been started in IIS:
In the left pane of IIS Manager under "Sites", select the appropriate site. If your site is configured under the "Default Web Site", select that one.
In the right pane under "Manage Website", there are "Start" and "Stop" links.
When the website is running, the Start icon (arrow) will be gray and its link will be disabled; the Stop icon (square) will be black and its link will be enabled.
When the website is NOT running, the Start arrow will be green and enabled; the Stop icon will be gray and disabled.
So if the Start link has a Green arrow by it, that means the website is NOT running, and you need to click to start it.
By default, web sites are started automatically when IIS is started or restarted.
But if you click the link to stop the site, it will remain stopped even after you reboot the computer or restart IIS. It won't be restarted until you click Start again.
I had also this situation where a local website hosted by IIS did not work. My site was already started but it seemed to lack the rights for an internet browser to access to the local site.
In my case I got the site working by giving the site's root folder (and its contents in the Windows 10 file system) the following usage rights:
Authenticated Users
This usage right can be set in folder properties and its security tab.
Other usage rights present are:
SYSTEM
My own account
Adminstrators (MACHINENAME\Admistrators)
I post this solution here in case someone is in trouble with the same issue.
An update: This 'Authenticated Users' group needs also permission to modify files and folders in case e.g. Wordpress is used as a local site and the adminstrator wants to e.g. update themes and plugins of the site.
If this permission is not set, Wordpress will fail to write the updates to the local folder. The message shown is: "Installation Failed: Could Not Create Directory".
However, please note that at the moment I cannot guarantee that these settings are completely safe and do not compromise your system for attackers etc. But I've taken the risk myself, and the settings will provide a working environment to develop locally.
some time this problem because the application pools is stopped after restart server machine this is problem happened me.Picture for clarification, enter image description here
I encountered this issue recently, and none of the other answers here helped me. I was unable to connect with http://localhost/mywebsite, but I could with http://127.0.0.1/mywebsite. I was able to put a bandaid on the issue by creating a new binding:
Type: https
IP address: All Unassigned
Port: 443
Host name: empty
[x] Disable Legacy TLS
SSL certificate: IIS Express Development Certificate
I could then connect with https://localhost/mywebsite. Hopefully this helps someone else!
I want to know when the IIS is stopped can I show a custom html page instead of 404 error message? I stop IIS with help of cmd(net stop WAS ). I have tried app_offline.htm. it works fine. But when I start deploy by stopping the IIS the html page is not shown. I have searched a lot for this. But everywhere the Q is about only stopping the site. I want to know the reason why I can't show and also if there is any solution to that please help me. I am almost new in professional line. And my senior won't believe me because I can't explain why doesn't it work.
The web page is able to be showed due to that the IIS provides the hosting service. As long as the related IIS service is stopped, these web pages no longer been served.
The blog written by IIS official shows the IIS core service used to host the web page.
https://blogs.iis.net/tomwoolums/the-services-behind-internet-information-services-7-0
Feel free to let me know if there is anything I can help with.
My website is working with some ISP while it is not working with others. Also not working from other countries.
The app is hosted at our company. Developed using sharepoint asp.net.
The app works at my home.
But if I visit the website at my brother's home who is registered to different ISP, the website opens and a login dialog appears. When entering correct username and password then submit , textboxs cleared and dialog come again.
The problem is happening with many visitors.
I just want to know what would be the problem! Does anyone faced such problem before?
I checked all IIS restrictions. There is no restrictions made.
I created a new app using sharepoint with login page and it works great.
somebody said that users with public ip can access the site while others with dhcp cannot. Can somebody explain that !
Some ISPs have transparent proxies in use. And some of them are accidentally (or even intentionally) broken and cache more, than they should. You can check whether that's the problem:
Set up your server to also allow https and then use that. You should move to https for privacy reasons anyways, so just do it now ;)
This way, the proxy can't do anything but to pass the data between client and server unmodified.
If that is not an option: Use tcpdump/wireshark/other-sniffer on both - client and server - at the same time and compare the logs. Did the second access even make it to the server?
Do you have a laptop/tablet/smartphone with which you can access the web server? Try moving that laptop from one location to the other and check, whether it works with that one laptop using one ISP and fails with the same laptop on the other ISP.
This should be a comment, but I do not have enough to post it as such.
Are sure that it is not a browser issue?
Is the login dialog from SharePoint, your app or the browser itself?
If it is from your app, can you debug it or write the log-in attempts in a log?
Every time I try to connect to any SharePoint site running on my customer server I get the following error.
An error occurred accessing your Microsoft SharePoint Foundation site
files. Authors - if authoring against a Web server, please contact the
Webmaster for this server's Web site. WebMasters - please see the
server's application event log for more details.
I already checked the sharepoint options in CA and in every site in the mentioned server. Everything seens correct but the error persists.
It looks like there is no direct relation to SharePoint and something else in the server but I was not able to determine what could cause such behaviour.
Hope someone here has something to say.
Well... After a very long and painful headache we were able to find out what was causing this malfunction.
It was a .net agent from New Relic. This agent is used to analyse traffic, page load time and some other cool things. It basicly add some javascript to the head session of every response our IIS make and this code send some data to New Relic servers that will be processed to build some reports about the applications running in the IIS.
In the end, I just disabled it and SPD turned back to life.
Thanks.
PS: Boland was in the right path. I were able to find out the solution using Fiddler to analyse the responses from IIS. Thanks.
You have to check the event log. Do you see any error there? If not, it must be a network issue. Firewall is rare, because SPD works on TCP/80.
my website opens with xx.xxx.xxx.xxx IP address till friday it was working fine..after wards not able view the site in webbrowser...what could be the problem ? how can we solve it?
My server with this IP is working and can able to view the updated data in database ..but not able to view, or open the page of website.before the website under IIS configuration was stooped and now started again..still no use..am couldnt view Login page at all.My application was developed in classic asp long back.Kindly give me any suggestion to this...its very urgent...
I tried browsing the website in IIS manger(server) .It showing page cannot be displayed.
Thanks in advance.
First, Don't Panic. Staying calm can avoid further damage.
While it's hard to tell what could be the problem, the first thing you can do is to "ping" the domain from terminal.Can you login remotely? "wget" (on linux) will download the files from website, and could help you see if the files on the site are still accessible. Check from different browsers or machines, if possible. I'm no expert in asp or IIS, so won't advice on that front. But once I had faced the same situation with my website. So I just called up the hosting service provider, and it turned out it was their problem, and they brought the server online. If it's okay from their end, you might have changed some configurations in your server or application or there might be some up-gradation changing parameters, or even an accidental deletion/ moving/ renaming of files. Just try to remember what are the things you did with your server and application, before it went down, and also ask your server administrator. That will surely help you understand the problem better, if not help to solve it right away.
Good Luck.