If, like me, you do all of your development locally using some sort of stack front-end like Local by FlyWheel or MAMP Pro, your productivity was likely crippled by the latest, unholy update. Evidently, Google has an axe to grind, as you may now get the ERR_CERT_COMMON_NAME_INVALID page any and every time you try to load a page or click a link on a locally-developed site that forces SSL.

This (sort of) worked for me. It still shows the certificate invalid, but Chrome doesn’t warn be about it with every click and page refresh. I only tested this on Chrome 58 on OS X Sierra.

  1. In Chrome’s address bar, type: chrome://flags
  2. Scroll down to the “Allow invalid certificates for resources loaded from localhost” option and click the Enable link.
  3. Click the RELAUNCH NOW button.



Leave a Reply

Your email address will not be published. * Denotes required field.
You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">

Tip: Do you want an image (avatar) next to your posts? Sign up for a free Gravatar account. It only takes 5 minutes - simply click the "Create Your Own Gravatar" button, provide your e-mail address and upload a photo to associate with it.