I have trusted the SSL and I can see this in KeyChain as a trusted SSL…I have also included all the Salt Auth codes in the wp-config file, but it keeps throwing back this error. I can see the website in a browser, but all of these errors are displayed above it (see attachment).
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.
UPDATE: This is deffo a Local WP issue as I’ve uploaded the exact same Theme to a live domain and the website is works perfectly. So frustrating, as I can;t even use Local WP as intended because of these errors. Please help and come up with a solution.
Hi there @epilo - are you able to access your site at all? Is there a plugin that may be causing the SSL error (I see “Type Kit” mentioned there)? If so, are you able to disable it and see if the error goes away?
Are you able to get a Local site running with an SLL + default settings?
Have you reviewed these troubleshooting tips for SSL?
Thank you for the response, much appreciated. I have resolved this, please read on.
The SSL is working fine and the cert is trusted, so wasn’t an issue with the SSL. I could access the site, but it was throwing back PHP errors breaking the UI. Both on the front end and the WP-Admin backend.
I have temporarily renamed the Redux Typekit Folder, found in the Redux Extensions plugin (Redux framework is a free-to-use option panel framework for WordPress themes) and is common. This stopped the errors, but that said, the theme works perfectly normal outside of Local WP…no errors.
So I have it working, but I have had to disable one folder - the Typekit Folder and ideally I need this in the theme and works fine outside of Local WP…so appears to be an issue with the code found in Typekit-client.php and Local WP.
Perhaps something to do with this code in the PHP file? As this was the error displayed on the screen breaking the UI (see previously attached file).