# Self-signed SSL cert w/ browser-sync localhost proxy (Chrome on Windows)

**URL:** https://discourse.roots.io/t/self-signed-ssl-cert-w-browser-sync-localhost-proxy-chrome-on-windows/5862
**Category:** sage
**Tags:** gulp
**Created:** 2016-02-07T22:37:43Z
**Posts:** 10
**Showing post:** 8 of 10

## Post 8 by @100wunder — 2018-05-29T17:10:19Z

In my case (macOS High Sierra, Chrome 66) the cert was still invalid resulting in error message: ERR\_CERT\_COMMON\_NAME\_INVALID

The solution was to add some extra parameter as described here: [https://stackoverflow.com/questions/43665243/invalid-self-signed-ssl-cert-subject-alternative-name-missing](https://stackoverflow.com/questions/43665243/invalid-self-signed-ssl-cert-subject-alternative-name-missing)

After that and adding the cert again to the keychain (and setting the trust right) the SSL cert went green eventually.

---

_[View the full topic](https://discourse.roots.io/t/self-signed-ssl-cert-w-browser-sync-localhost-proxy-chrome-on-windows/5862)._