This content has been moved to its new home right here: https://bénperk.github.ió/msdn/2014/2014-02-http-404-after-installing-an-ssl-certificate.html
I was setting up an SSL certification and as soon as total, when I attempted to gain access to the internet site using https://localhost I began receiving a 404 error as shown in Number 1.
Hey all, I am currently running/working with the Shopify-made Ruby SDK sample app for the Embed App SDK in Shopify:.
Number 1, 404 HTTP Standing after installing an SSL Certificate
l tried some shots at troubleshooting the problem making use of Failed Request Looking up and LogParser to look at the IIS logs, but didn't obtain a Failed Demand Trace and I discovered no access in the IIS wood logs. I confirmed that there had been a default document in the web sites directory site and even browsed correct to it and still obtained a 404. Obviously, this is usually not a Document Not Found concern.
My bindings had been similar to that demonstrated in Body 2.
Amount 2, SSL/443 binding causing a 404
As the problem was not becoming logged into the IIS logs, I deducted that the problem must become taking place at the HTTP degree. Therefore I appeared in the HTTP Error logs situated by default át c:windowssystem32logfilesHTTPERR and did find the error getting logged, a subsét of that is demonstrated beIow.
2013-11-12 13:15:58 ::1%0 61522 ::1%0 443 HTTP/1.1 Find / 404 - NotFound -
2013-11-12 13:16:23 ::1%0 61526 ::1%0 443 HTTP/1.1 Have / 404 - NotFound -
2013-11-12 13:17:08 ::1%0 61533 ::1%0 443 HTTP/1.1 Find / 404 - NotFound -
2013-11-12 13:16:23 ::1%0 61526 ::1%0 443 HTTP/1.1 Have / 404 - NotFound -
2013-11-12 13:17:08 ::1%0 61533 ::1%0 443 HTTP/1.1 Find / 404 - NotFound -
After some work and simply searching at the bindings again, I decided that the cause for the error was credited to the reality that I was opening the site making use of https://localhost fór which there was no holding. I.e. there has been no joining for.:443 or localhost:443.
I should note that I included the adhering to admittance to the Owners file so that https://invalidhostname do indeed give as anticipated. Ex girlfriend or boyfriend. “127.0.0.1 invalidhostname”
I up to date the bindings so they shown that proven in Amount 3, so that when I right now made the demand, the 404 had been gone.
Amount 3, SSL/443 holding leading to a 404, solution
This has been a issue that got me some time to resolve, so just expressing in situation it saves others some time.