No matter what I do, the SSL certificates will not stay trusted in Windows 10. I can restart my browser, run as administrator, etc and the SSL doesn’t stick. This is causing an issue when trying to pull from APIS (like YouTube) that require a secure connection.
Troubleshooting Questions
Does this happen for all sites in Local, or just one in particular?
This happens in all my sites
Are you able to create a new, plain WordPress site in Local and access it in a Browser?
Yes I can create sites no problem
Replication
Describe the steps that others can take to replicate this issue. If you have screenshots that can help clarify what is happening, please include them!
System Details
Which version of Local is being used?
Version 6.3.0+5756
What Operating System (OS) and OS version is being used?
For example: macOS Catalina or Windows 10 Professional
Windows 10
Attach the Local Log. See this Help Doc for instructions on how to do so:
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
I’m having the same issue with Win 10 Pro. But once I open the site in the browser I’m seeing https and there’s no warning about unsecure. So maybe it seems Win 10 recognizes the TRUST to TRUSTED but for some reason Local loses track.
More or less, for me atm it’s a non-issue as long as the brower uses https
drikfan, not me. (Mac, Catalina) I reverted to 6.3.0, have certs that say “always trusted” in my keychain, and even when I allow an exception in Firefox, it still is not a secure connection. Same behavior in Chrome. Frustrating.
@yomartin and @drikfan - the Mac issues will be resolved in Local v6.4.1 which will be available on our releases page shortly. www.localwp.com/releases. We had several users confirm the fix was working for them in the Beta build we published last week.
As for Windows (original post here), there does seem to be a UI bug specific to Windows like mfs_au explains here - SSL Will Not Stay Trusted - #3 by mfs_au. The certificate is trusted, but the UI reverts back. The developers started taking a look at this this morning.
I’ve been dealing with this issue consistently on Windows 10 for years, since probably the 5.x.x days. I’m not sure I remember a time when it stayed “trusted” in the UI.
Hey @alexwright - this thread is about Windows specifically and the UI not reflecting the accurate SSL trust status. This has been fixed with a previous Local release (Local 6.5.1).
Here is a recent reply for SSL troubleshooting - SSL certificates no longer work in Google Chrome - #42 by austinwendt. If you update to the latest Local and are still experiencing the issue after following the steps in the link, please reply in that thread and we can take a look.