4

I have followed these instructions (available from Wayback Machine in case they disappear) to add the certificate of my Asus Router to the keychain but Chrome still refuses to trust it, with the error message "NET::ERR_CERT_COMMON_NAME_INVALID". However, Safari accepts it.

I have spent a lot of time on Google looking for answers and there are a lot of articles about this but they seem inconclusive (and many are old).

So how do I make this work?

In case it matters, the router is available both at 192.168.1.1 and router.asus.com (in both cases I use the port 8443).

Bonus: How do I make this certificate work from the outside (both in the case of a FQDN as well as when connecting using the IP-number).

1

The web page you linked to is old and now incorrect.

Chrome does not use the MacOS keychain any more. Safari does use this so that is why it works.

For more details see this answer.

  • 2
    That applies to passwords (which I was aware of), not certificates. Chrome now offers its own password management but, AFAIK, not its own certificate management. Do you have any other source that can confirm that, and how, Chrome manages certificates independent of the keychain? – d-b Dec 16 '17 at 23:20
  • 1
    When I click "manage certificates" in Chrome 69, it opens the Mac keychain access app. So it's still suing the keychain. – Steve Jul 18 '18 at 18:41

You must log in to answer this question.

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