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!
Our website not running on new server Tour website we have 2 servers one of them the site working good, we have moved the portal to other server, so when we point the dns it is not working...Web not working and then you can see the panel of that server in second imageCWP web control panel I need the solution, kindly give the proper solution...
You are using CentOS Web panel as the hosting control panel. While browsing the website check the apache error logs on the server at path
/usr/local/apache/logs/
and those logs will give you idea of whats happening.
When I publish or restart my web app it loads very slowly the first time, then when I refresh with F5 it is ok again. what could it be?
It will happen with Windows Azure Websites. Windows Azure Websites are running in shared pool of resources and uses the concept of hot (active) and cold (inactive) sites in which if a websites has no active connection for x amount of time, the site goes into cold state means the host IIS process exits. When a new connection is made to that websites it takes a few seconds to get the site ready and working. Depend on how your first page code is, the time to load the site for the first time varies.
The IIS takes a while to boot up after you upload new files to the app container. Application Initialization module and deployment slot swap also takes several time.
So the first page hit after you've updated the app will be slower. Also Azure Web Apps get dehydrated after a period of inactivity. This also causes the first page hit to be very slow if the page hasn't been accessed in a while.
To combat this, in the Application Settings for the web app, you can find a setting called Always On, which basically pings your page every couple minutes to keep the app hydrated and responsive.
For more details, you could refer to this blog.
As juunas said, you could also use Razor view pre-compilation to speed up the initial loads. Otherwise the app must compile the views at run-time when they are first rendered.
We have two servers on a cluster, say server1 and server2. We have these for load sharing and backup if one server is down.
We have many HNSC web Apps each containing a bunch of sites.
One particular HNSC web application is not working on one server (server2) but only works on server1. It was working fine till 2 days ago !
Other HNSC web Apps are working fine on both servers. If SharePoint architecture or software updates were the case, then no other web app or site collection would be working on the faulty server, but others are working fine.
The sites within this particular web App are giving the following error in browser window when they hit server2:
Server error: http://go.microsoft.com/fwlink?LinkID=177673
When they hit server 1, they run fine.
Please help.
Looks like it was a problem with sharepoint software updates on one server. The IT Team had installed updates on one server but not the other.
Reason why only 1 webApp (and Hnsc site collections inside it) were giving error is because they were created after the updates were done on one server.
Solution: IT Team did the updates on the other server as well, and all worked fine.
im running a sharepoint services website on my laptop using a virtual server on the same laptop. i need to show other people (on external machines) the website in a development stage. i have sent them the same address i am using to open and ive given them their own log ons- they work on my machine.
the problem is that the site comes up with the IE cannot display the webpage even before they get to the log on stage. ive only been using sharepoint for a few days and dont really know my way around- can anyone help please
Try to use the IIS to map your internal server outside.