Solved IIS Running But Cannot Connect
-
This has to be something silly but I figured you guys could get me through it far faster than if I was digging on my own. I have a Server 2012 R2 IIS setup and I had an ASP.NET application that I was porting working fine. Then the machine rebooted and now it will not connect. I get a 503 error "service is unavailable" when going to the same URL that worked before. In fact, even just
http://localhost/gives that error.The service is running. If I go into the IIS Manager, the site says it is up. How do I track down the source of the 503?
-
What do the logs say?
-
Don't see anything in the logs related to any IIS errors.
-
Did a firewall setting get changed?
Is this a public facing website?
-
@DustinB3403 said:
Is this a public facing website?
No, will face into the LAN only. It's just for internal use. And I am only testing from the local machine right now, and even that is not working.
-
@DustinB3403 said:
Did a firewall setting get changed?
No, it is centrally controlled via GPO. Nothing has changed. And I am testing using the loopback which should not hit it and did not hit the firewall before. And HTTP is allowed through it, too.
-
Is this just a basic HTML website? It sounds like you just have a hung service.
-
@DustinB3403 said:
Is this just a basic HTML website? It sounds like you just have a hung service.
He stated it was an application. First post wasn't that far up.
-
@JaredBusch said:
@DustinB3403 said:
Is this just a basic HTML website? It sounds like you just have a hung service.
He stated it was an application. First post wasn't that far up.
Sorry duh.
-
@Reid-Cooper what application are you running?
-
A 503 means that IIS is responding but that there is an error. Here are the possibilities for the error code: https://technet.microsoft.com/en-us/library/cc781893(v=ws.10).aspx
Because a 503 and not a "Page Cannot Be Displayed" error is what is coming through, it sounds like we are past the Firewall point and are dealing with something wrong with IIS configuration not Firewall. This implies (I think) that port 80 is making it through end to end to deliver the error code.
-
@DustinB3403 said:
Is this just a basic HTML website? It sounds like you just have a hung service.
-
@DustinB3403 said:
@Reid-Cooper what application are you running?
It's a small semi-custom thing that we have run for years but is being moved to a new server.
-
@Reid-Cooper said:
@DustinB3403 said:
Is this just a basic HTML website? It sounds like you just have a hung service.
Are you certain there are no logs?
By default all sites should log here:%SystemDrive%\inetpub\logs\LogFiles -
@Reid-Cooper said:
Wait 2.0? Did you properly configure the pool? Gimme a minute and I can log into a Server 2012 R2 with IIS running.
-
@JaredBusch said:
@Reid-Cooper said:
Wait 2.0? Did you properly configure the pool? Gimme a minute and I can log into a Server 2012 R2 with IIS running.
This is the application pool. You may also need to select classic pipeline mode.
-
@JaredBusch said:
Are you certain there are no logs?
No, only certain that I didn't find anything logged
I'll check again. -
@JaredBusch said:
@Reid-Cooper said:
Wait 2.0? Did you properly configure the pool? Gimme a minute and I can log into a Server 2012 R2 with IIS running.
Yes, very old. And I "did" have it configured properly, it was running fine before the reboot. So at least at some point it was working as it should.
-
@JaredBusch ah ha, there we go! The 2.0 pool had "stopped" for some reason. I started it and the site came up. Thanks!
-
There were two application pools, one for 2.0 Integrated that was running, and one for 2.0 Classic which had stopped. Classic was the one that was needed.
