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!
Looks like this might be related:
I’m seeing this same issue. Looks like the generated cert is missing the Subject Alt Name, which Chrome now requires.
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)
jb510
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.
Same issue here. Hope someone can give some pointers on how to resolve this problem. Thanks!
Having the same issue here. Also running Chrome Version 58.0.3029.81 (64-bit).
clay
8
Hi all,
This will be resolved in the next release of Local.
We’ll have more details about it soon
.
I’m going to go ahead and close this thread since it’s confirmed. Feel free to
benjamin’s original post if you’re running into this issue.