Invalid vCenter Cert using macOS Catalina and Chrome

I had redeployed my home lab vCenter appliance, and upon attempting to access the vCenter UI, I was denied access and encountered the following error “NET::ERR_CERT_INVALID

Details in the Error normally uses encryption to protect your information. When Google Chrome tried to connect to this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.

You cannot visit at the moment because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.


I did a bit of digging around, and it seems to be a widespread issue with macOS Catalina and Google Chrome. Also, my previous vCenter installation had a signed certificate from ZeroSSL, which I believe is why I didn’t exhibit the issue before redeploying the appliance. 

Fortunately, the fix was surprisingly easy. When you are on the error page, type the characters “thisisunsafe“, and you will be directed to the vCenter UI. The fix was permanent unless Google Chrome settings were reset.

If you would like to install a free SSL certificate for your vCenter, please check out this blog post, Replace Default vCenter Certificate with a Free Let’s Encrypt SSL

I hope you found this information helpful, feel free to comment below 🙂

35 comments Add yours
    1. No worries man, glad you found it useful. To be honest I had resolved if before then forgot how I fixed it, so I decided to post it this time so I could refer back in 3 months time when I forget again 😜

  1. THANK YOU! This has been driving me crazy. I cannot believe you figured this out. Worked on the first try.

  2. Thank you. This oddball solution worked on Opera as well. I’ve been tearing my hair out for over a week trying to figure out what happened to suddenly block so many random sites, and most of the “fixes” might as well have been written in Greek! May your week be exceptionally lovely!

  3. It worked for me too. It’s wack… am I reading this correctly in that it has somethinng to do with vServer? What is vServer and what does it have to do with chrome? Amused that it works and confused as to how. I used the fix on chrome with various random sites.

  4. I’ve literally been looking months for a fix to this, it happens on like 30% of the sites I try to open on chrome, driving me crazy. Can’t believe it was this simple – thank you!!!!

  5. OMG it worked! It works for MacOS Big Sur and Chrome as well. The solutions seems so simple… But I I have to ask the question: is it safe to do that? I guess as long as we are certain that the site is legit, there should be no other concerns like insecure connections, etc right?

  6. that was frigging M A G I C, also i’m cackling that chrome’s ‘safe word’ is ‘thisisunsafe’ thank you for extending the life of my 2007 imac

  7. It worked when I was trying to view quora, can’t believe you solved it, one slight issue though, it got stuck in the loading screen all i see is the logo and then it says ” Something went wrong. Wait a moment and try again.” after a while

  8. oh man what a save! I’ll have to type it everytime for now but this is a great workaround man–You saved me hours today!

  9. That fix actually worked. Thought it was joke. Didn’t know that characters typed in to the keyboard without selecting text boxes can affect anything. Thank you

  10. I cannot believe this worked!!! can someone explain why that this works? I’m intrigued!!

  11. Thanks for this! Has anyone discovered a permanent way to avoid the problem of typing “thisisunsafe” every time?

  12. That is actually hilarious how that works. There is something so beautiful about obvious subtleties in complex machinery.

Leave a Reply