0

Starting 4 days ago (the date might be relevant if some updates came along), Chrome on MacOS started rejecting self-signed certificates. It includes things like Vagrant boxes and the Synology NAS web interface.

While with Chrome under Windows I can still click "advanced" and chose to "accept the risk and continue", that option is missing under Mac.

Is there any Flag or Setting to reintroduce that option?

2

Try to run the following command from the terminal and relaunch Chrome

defaults write com.google.Chrome EnableCommonNameFallbackForLocalAnchors -bool true

This can help you to solve your issue.

Or

If you need a workaround to get the site working without replacing the certificate you can do the following.

  1. Download the certificate from the server (using another browser or with openssl)
  2. Install the certificate into Keychain Access under the login store
  3. Set the certificate to "always trust" by double clicking on it once it's been installed.
2
  • Thanks! Unfortunately that had no visible effect. – Zsolt Szilagy Nov 22 '19 at 15:11
  • @ZsoltSzilagy: I updated my answer with another solution too. Give a try and see how it goes. – Udhy Nov 22 '19 at 15:28
-1

using Chrome Version 90.0.4430.72 (Official Build) (x86_64) on macos Catalina 10.15.7 accessing locally hosted VMs on VM Fusion v12

Certs have stopped being accepted even when they are in the keychain And after the "defaults write" suggestion above

This issue is happening with both self signed and root/ca signed certs

other users with similar macos/chrome/vmf versions are not experiencing the chrome server cert rejection and it seems a local configuration issue

any idea ?

thanks

another macos device using Chrome 87.0.4280.163 works fine and as expected not sure why 90.0.4430.72 is not

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .