Chrome 58 SSL Certificates Not Trusted

Support
1

Hey Clay!

Looks like Chrome 58 is being a jerk. After the update all local SSL certificates are no longer trusted. If you try to re-trust them, nothing changes:

I’m on Chrome Version 58.0.3029.81 (64-bit).

I figured I’d let you know if there is some new way to trust certificates locally that Local needs to update.

Thanks!

12 Likes
2

Looks like this might be related:

2 Likes
3

I’m seeing this same issue. Looks like the generated cert is missing the Subject Alt Name, which Chrome now requires.

4 Likes
4

I can confirm I’m seeing this same issue for my sites with generated certs in Local. Running Chrome 58.0.3029.81 (64-bit)

1 Like
5

Same here… looking at the Local generated certs they are indeed using the common name field.

If anyone finds an easy way to add a SAN and resign a certificate let us know… otherwise here’s hoping Clay/FlyWheel get this update ASAP.

1 Like
6

Same issue here. Hope someone can give some pointers on how to resolve this problem. Thanks!

1 Like
7

Having the same issue here. Also running Chrome Version 58.0.3029.81 (64-bit).

1 Like
8

Hi all,

This will be resolved in the next release of Local.

We’ll have more details about it soon :slight_smile:.

I’m going to go ahead and close this thread since it’s confirmed. Feel free to :heart: benjamin’s original post if you’re running into this issue.

1 Like