How to make SECURE? (SSL Trust on local)

I’ve got my local site setup like this with https specified on both lines.

And when I launch ADMIN from Local it shows as Secure:
2020-08-28_22-03-11

HOWEVER, if I launch VIEW SITE or I do any editing of the website, it becomes Not Secure:
2020-08-28_22-02-52

ALSO, I noticed that in the Local app - if I click TRUST, it will indicate that it’s trusted while selected but if I navigate to another site in the list and come back to this one, it tells me again that the site is not trusted. Like it doesn’t stick.

This is currently happening across the board for all my websites on local dev.
Can someone please help me make the sites secure on local?

@clay Any docs on how to properly setup ssl on local? Maybe I’m wrong to assume that it’s just a matter of setting the URLs to https in WordPress?

Does ANYONE have any answer?? I am struggling on the same issue.

1 Like

Presumably your SSL is setup correctly already since when you visit the https version of your site it works (rather than showing an SSL cert error), which means you’ll need to do a search+replace on your existing links (since WordPress saves the full, absolute url to the database) and then setup something for the server to force pages to go from http to https

  1. Install a plugin which can do search+replace on your database, I recommend WP DB Migrate. This will fix up your absolute urls for page links and things like images

  2. Setup server redirects. I’m not sure whats involved on nginx, but on apache servers you’ll need to modify the .htaccess file to redirect http traffic to https. Search up something like “htaccess redirect http to https” and you should get a lot of good results

Thank you for chiming in! This issue has been going on for a while it’s nice to get a lead. I used the WP DB Migrate plugin to do a search/replace of the entire URL but converted to https. (ex: http://testsite.local replace with https://testsite.local). It worked for most of the sites but not all. So then I realized that I should have probably just been search/replacing the http part, not the entire URL.

When I did that, this is what I got:

Not sure why it added an extra “s”. That’s not what i asked of it…but I’m presuming that this is why I’m getting the Fix It warning in Local?

Was I not supposed to do a search/replace ONLY on “http”?

ALSO, I should add that in none of these cases did “TRUST” stick inside the LOCAL app. I kept having to push the TRUST button again, even for those sites where the padlock issue was resolved.

Your search replace for http picked up the http in https, so anything which was https is now httpss. Just do a search replace for httpss:// to https:// and it’ll fix it.

ALSO, I should add that in none of these cases did “TRUST” stick inside the LOCAL app. I kept having to push the TRUST button again, even for those sites where the padlock issue was resolved.

Mine had that too, assuming its a known bug.

1 Like

Thank you -
I hope they DO know its a bug and they’ll squash it soon!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.