I'm developing a site for a company from a local server. The site back-end is Hybris/Java and have no access to it.

The site is configured to serve pages as https but, as it's run on a local machine, the certificate is seen as invalid by browsers.

This is not a problem with Chrome or Firefox as you can add an exception thus 'trusting' the dodgy certificate.

However IE11 & Edge don't give the option to add the exception and simply won't display the site.

Is there a work around for this ?

Screenshot from IE11

migrated from webmasters.stackexchange.com May 8 at 23:47

This question came from our site for pro webmasters.

  • "seen as invalid by browsers" - do you mean it's self signed? "and simply won't display the site" - In IE11 you should get the option to "Continue to this website (not recommended)"? – MrWhite May 8 at 14:12
  • @mrWhite - Added a screenshot. I suspect that it's a proper cert but for the proper website, not our local development versions. And, as you can see, I don't get the 'continue' option. – Pat Dobson May 8 at 16:01
  • I believe these two browsers may use Windows' own certificate store, but I may be mistaken. – Maximillian Laumeister May 9 at 3:55
  • The message seems to indicate weak protocol or ciphers. Chrome just (v72) deprecated TLS 1.0, and IE is about to (I believe), but if it's fine in Chrome 72, it's probably not barking @ the protocol. Does the cert have a Subject Alternative Names attribute with your DNS name (bbr-uk.local) in it? – Dallas Jun 3 at 19:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy