Skip to main content
Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Firefox uses its own certificate store. So Firefox is rejecting the secure connection since the certificate from its perspective isn't valid.
    – Ramhound
    Commented Apr 24, 2015 at 16:28
  • 2
    I'm surprised http://localhost:443 (unsecured HTTP over port 443) works at all. It almost sounds like you have standard HTTP bound to port 443 somehow. I tried that on an Apache site or two that have SSL running properly, and I just get a blank page in IE rather than content or a security warning. Chrome and Firefox give a warning that I'm trying to talk HTTP on an HTTPS port. Does https://localhost:80 give you different results?
    – GuitarPicker
    Commented Apr 24, 2015 at 16:36