As of yesterday (Oct 28), all LOCAL sites that have a TRUSTED certificate are no longer working in Google Chrome. All non-SSL LOCAL sites are working fine. Working fine in both Safari and Firefox
System Details
Which version of Local is being used?
6.1.5
What Operating System (OS) and OS version is being used?
Big Sur - 11.6
Attach the Local Log. See this Community Forum post 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.
Seeing this as well, It doesn’t matter which browser. It is also impacting if you are making any SoapClient connections as well. Even if you have ssl_verify to 0 it still is failing due to an expired cert
I also am seeing this and Chrome isn’t being helpful and telling me exactly why it doesn’t like the certificate anymore.
Creating a new site and trusting that certificate seems to work.
I also tried deleting the old certificate in Keychain, restarting Local and then clicking the “trust” button again to generate a new certificate and finally trust that new certificate in Keychain again.
Let me clarify what’s going on for me. I am the one who started this thread.
I have over 50 local flywheel sites and I’ve been using this process for building sites for years now. This problem began very suddenly the other day. No software changes that I’m aware of, unless there was a Chrome update I missed.
It is ONLY happening in Chrome. I’ve tried clearing the cache and using incognito windows.
It is ONLY happening for sites that I have pulled from Flywheel that are secure and therefore use “https” locally. Any site that doesn’t yet have SSL on Flywheel is working fine. Any new LOCAL site is fine IN CHROME. It’s AFTER interacting with FLYWHEEL hosting that things go off the rails.
I have restarted everything several times just to be sure.
Here is the error. pna.local is just one of the sites I’m using as this example.
Your connection is not private
Attackers might be trying to steal your information from pna.local (for example, passwords, messages, or credit cards). Learn more
pna.local normally uses encryption to protect your information. When Chrome tried to connect to pna.local this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be pna.local, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
You cannot visit pna.local right now because the website sent scrambled credentials that Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.
One last thing. I think this started when the latest LOCAL update happened (release Oct 14). Looking back it was very recently - maybe in the last week - that I go prompted that there was a new version of LOCAL. It might have been the day this started.
Thanks for providing that example certificate! I still have to check on a few things, but I wonder if somehow, the cert is being corrupted when generating that certificate?
