UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.68 Safari/537.36

Example URL:
https://localhost

Steps to reproduce the problem:
1. Run the attached AbyssWebServer.exe file. This will install the free web server locally on the machine. It will also run a .bat file as an administrator to install the certificates into the Trusted Root Certificate Authorities for the local machine. The bat file will also install the web server as a windows service and start it. There are two certificates: "eNcounter3.crt" is the CA and "localhost.crt" is the client certificate.
2. Copy over the attached index.html file to "C:\Abyss Web Server\htdocs".
3. Navigate chrome to https://localhost

What is the expected behavior?
Since the root certificate and the client certificate are installed in the Trusted Root CA store, Chrome should display a green lock for the web page.

What went wrong?
"https" has a red slash through it and the privacy error page is displayed with the error "NET::ERR_CERT_COMMON_NAME_INVALID"

Did this work before? Yes 57

Chrome version: 58.0.3029.68  Channel: beta
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 25.0.0.148

These certificates are used for products that require HTTPS when navigating to a locally served page. It has worked in Chrome 57 and earlier versions dating back a few years, so I labeled this as a regression.