This solved my issue of "503 “Service Unavailable”" over HTTPS.
Disable Remote GUI if you don't want it enabled, then Save. Enable Remote GUI and change the port to something other than 443 (such as 4433), then Save. Click on Remote GUI on the left side menu under Remote Management. If Port 443 is already taken by the router's Remote GUI Management. Per the answer here in this link, do:Ĭommon error: "The defined port or port range is in use by another port forwarding or application rule." Lesson learned, if you are using a router branded by CenturyLink or other company that does the same, maybe the same applies. But because I was using a modem branded CenturyLink, the router's Remote GUI Management was using the port. I checked the modem port and realized it required port 443 forwarding enabled. Everything looked fine on the IIS side: SSL certificate, ports, site running, etc. I had a similar issue getting "503 “Service Unavailable”" over HTTPS, HTTP when I checked the console in Firefox. For instance if port 80 is reserved and 443 is not, then the site over HTTPS would work, while HTTP would not. 
Note, that you can also check port 80, or any other port using this method.
If there is nothing there, then this might not be the issue. If there is a need to reserve port 443 for an application running outside of IIS, it needs to be registered with an application path (i.e. Port 443 is completely reserved and is blocking IIS. If something is there, then this is your problem. 
Here are the steps to determine if this is the problem and how to resolve: Furthermore, applications that run in IIS do not need explicit reservations to run, only non-IIS applications have to reserve a URL namespace if they want to use HTTP to listen for requests." The problem in this case is that everything on port 443 has been reserved and "prevents W3SVC from obtaining the rights to listen on port 80 when it tries to start the site. The commenter Chad Cothern on this blog had the answer and linked to this Microsoft Blog by BretB.
Site > Advanced Settings > Enabled Protocols > http, https. NET code as the 503 error comes back immediately, even after an IIS reset, or web.config modification Reason: Site/.NET already runs successfully over HTTP, and the site never appears to hit the. Again, the same App Pool that runs successfully under HTTP is used with HTTPS Reason: The same App Pool that runs successfully under HTTP is used with HTTPS. Here are the solutions that I've seen for similar problems that do not apply to this scenario: The SSL certificate used on the site self-generated/self-signed. 
When I run the site over HTTPS, I immediately get an HTTP 503 error "Service Unavailable". When I access the site over HTTP, everything works fine.
0 kommentar(er)
