New issue
Advanced search Search tips

Issue 608018 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome Windows 10: Self signed certificate not working

Reported by davidvie...@gmail.com, Apr 29 2016

Issue description

Chrome Version       : 50.0.2661.87

What steps will reproduce the problem?
Go to the site (which points via hosts file to 127.0.0.1): E.g. https://www.my-local-dev-page.com
Get an error: NET::ERR_CERT_COMMON_NAME_INVALID
I click continue
I click on the red lock in the top left corner inside the certificate popup I choose "export to file"
I choose "DER-codiert-binär X.509 (.CER)"
I click next and close chrome
I import this CER file both via windows user certificates and also in the chrome settings in the ssl path of the root authorities
I open up chrome and the error comes again
If I click again "continue", it seems that somehow it is working, but after a few requests, it is falling back and the error comes again.


What is the expected result?
ALL requests in the future work without a problem and that a green lock is shown on the top left.


What happens instead?
Nearly on every tenth reload I get a certificate warning (always after browser restart) and a red lock is shown in the top left corner.
 
Components: Internals>Network>SSL
Labels: Needs-Feedback
Please attach a net-internals log per these instructions. Thanks!
https://dev.chromium.org/for-testers/providing-network-details
This file is recorded when doing the following steps:

Go to the site (which points via hosts file to 127.0.0.1): E.g. https://www.my-local-dev-page.com
Get an error: NET::ERR_CERT_COMMON_NAME_INVALID
I click continue
I click on the red lock in the top left corner inside the certificate popup I choose "export to file"
I choose "DER-codiert-binär X.509 (.CER)"
I click next and close chrome
I import this CER file both via windows user certificates and also in the chrome settings in the ssl path of the root authorities
chromelog_before_restart.txt
3.8 MB View Download
This file is recorded when doing the last steps:

I open up chrome and the error comes again
If I click again "continue", it seems that somehow it is working, but after a few requests, it is falling back and the error comes again.
chromelog_after_restart.txt
2.6 MB View Download
ERR_CERT_COMMON_NAME_INVALID is not overridden by importing a root certificate. Or any certificate.
Thanks for your answer!

I am stunned. How can I then develop locally with a self signed certificate? Am I doing something completely wrong?

What is the way or is this not possible?
You need to generate your certificates with the right name.
Thanks, that was the case. The CN was wrong! Sorry, this topic can be closed!
Status: WontFix (was: Unconfirmed)

Comment 10 Deleted

Sign in to add a comment