Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR_CERT_COMMON_NAME_INVALID in Chrome, Android, Opera #3

Open
corysimmons opened this issue Mar 15, 2018 · 2 comments
Open

ERR_CERT_COMMON_NAME_INVALID in Chrome, Android, Opera #3

corysimmons opened this issue Mar 15, 2018 · 2 comments

Comments

@corysimmons
Copy link

https://www.chromestatus.com/feature/4981025180483584 breaks this plugin. Looks like it needs a subjectAltName https://security.stackexchange.com/questions/74345/provide-subjectaltname-to-openssl-directly-on-command-line

@neverendingqs
Copy link
Owner

I took a stab at it, but don't understand openssl enough to make this change. Would you be able to provide an example of how the command openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 999999 -nodes should change?

Side question: are you able to proceed regardless? I get a NET::ERR_CERT_AUTHORITY_INVALID on chrome, but am still able to ignore these errors, and I assumed any error is ignorable.

@corysimmons
Copy link
Author

I haven't taken a stab at it yet but I assume one of those SO answers might help. I know that BrowserSync used to work as well (haven't confirmed recent versions).

Here's his gen https://github.com/BrowserSync/browser-sync/blob/ca41bf1668964d676befd664e163a85f1478051d/certs/gen.sh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants