ERR_CERT_COMMON_NAME_INVALID

[DeVaultSetter]

On Chrome, the following comes up with a red warning:

Your connection is not private
Attackers might be trying to steal your information from stearnvault.com (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
To get Chrome’s highest level of security, turn on enhanced protection
stearnvault.com normally uses encryption to protect your information. When Chrome tried to connect to stearnvault.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be stearnvault.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
You cannot visit stearnvault.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.

Similar greetings from MS Edge, and presumably other browsers. Not possible to log in from a standard Chrome tab, possible in a Chrome Incognito Window, or MS Edge, other browsers not tested.
Googling the error code can bring up a range of workarounds, in the case of Stearnvault, it’s unsurprisingly an issue with the certificate itself, as the error indeed indicates.
Solution: Report to Site Admin.

[DeVaultSetter]

Happened again at the day of this posting, AutoSSL times out, the internal cPanel error with the certificates was:

The installed certificate does not cover this domain

All of a sudden, three hours later, the certificates are fine. No word from the providers as yet, so just in case they missed it, requested a reason for the outage. The certificates are to expire in two weeks time, wonder if this is some kind of “nudge” to make preparations for their renewal, or just another bog standard glitchy software stall.

[Spastic Hamburger]

May have been a renewal hiccup. Now all of the subdomains are showing up as they should in the certificate information with the next renewal set for April. I know in the Linode, it would sometimes take a day or so for the renewal to complete. Never did figure out why. It occurred even when I would run the command manually

In any case, it’s good to be back. 🙂

We’ll plan to repeat the maneuver in three months 😛

• This reply was modified 1 week, 4 days ago by Spastic Hamburger.

[DeVaultSetter]

🙂
How odd, the dates for expiry on the certs (excluding the mail related) were set for the 13th of February. Looks like they have been manually regenerated then, still no confirmation from the providers. The full WHM access allows for some AutoSSL tweakage, not sure if it would have helped us here though.
Edit: They came back with:

This may be considered as a slight glitch as Auto SSL is being renewed automatically.

Despite the overly technical overtones given in the explanation, we will also happily note the mention of Bethesda Softworks in Wikipedia’s Video game glitches. 😛

• This reply was modified 1 week ago by DeVaultSetter.

[Spastic Hamburger]

Good to know that nothing is seriously broken 🙂

I still haven’t played Eternal Darkness. It really needs to be released again 🙁

[Author]

Posts