# How to use with https://localhost:3000

**URL:** https://discourse.roots.io/t/how-to-use-with-https-localhost-3000/20933
**Category:** sage
**Created:** 2021-06-10T23:26:43Z
**Posts:** 14
**Showing post:** 14 of 14

## Post 14 by @strarsis — 2021-06-12T08:35:39Z

Does this help?

> [@Self-signed SSL cert w/ browser-sync localhost proxy (Chrome on Windows)](https://discourse.roots.io/t/self-signed-ssl-cert-w-browser-sync-localhost-proxy-chrome-on-windows/5862/8):
>
> 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/how-to-use-with-https-localhost-3000/20933)._