ERR_CERT_COMMON_NAME_INVALID

[ghost]

I follow these two instruction to address the cert errors, but both didn't work.

Option 1: Tell your browser to explicitly trust the certificate. You can do this in your browser's "advanced settings" tab, by installing sslserver/certs/development.crt as a trusted certificate. The mechanism for this varies from browser to browser.

Option 2: Use a certificate from a CA that your browser trusts, for example Letsencrypt. If you have a certificate/key pair from a certificate authority, you can tell Django SSL Server to use it with the following arguments:

[ssokolow]

I just ran into the same problem.

1. I needed to test on Android with browser features that are only enabled for HTTPS-served sites.
2. I used Firefox Mobile and it worked fine.
3. I needed to test some features Firefox Mobile hasn't implemented yet.
4. It turns out Chrome for Android no longer has an option to trust the site unless you jump through a ton of hoops... and I got stuck when the instructions didn't work as they should. (ie. The browser acknowledged the option had been set, but still refused.)
5. I added django-sslserver's CA to the test phone and ran up against ERR_CERT_COMMON_NAME_INVALID.

It looks like I'm going to have to generate a new cert with the actual site hostname baked into it to fix that, and I really don't like how the README seems to be indicating that I'm going to have to write a wrapper script around manage.py runsslserver rather than just specifying the custom cert to use in a config file.

It's a very not-Django-ish way to do things.