After domain change, cannot re-trust certificate - 'trust button' greyed out

Support
,
1

Issue Summary

When I change the domain name on a local site, then restart, the certificate is no longer valid in my browser. In the localwp panel, the ‘trust’ button is greyed out. How can i reset the button so that I can ‘trust’ the new domain*?

(* and, please tell me that this is a bug you are working on. I don’t want this to become a huge rabbit hole messing with command lines and certificates. I just want this to work as easily as it did when i set up the site. We all have full days of work)

Troubleshooting Questions

  • Does this happen for all sites in Local, or just one in particular?

Any site, it happened on several when I changed the local domain, or moved the file paths around, which happens often in local development

  • Are you able to create a new, plain WordPress site in Local and access it in a Browser?

When I create a new site, the trust button works (yay)! But this is a different issue - this is after I change the local domain name, and then I can’t ‘re-trust’ it at the new domain

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!

When I change the domain name on a local site, then restart, the certificate is no longer valid in my browser. In the localwp panel, the ‘trust’ button is greyed out. How can i reset the button so that I can ‘trust’ the new domain?

System Details

  • Which version of Local is being used?

6.2.1+5711 (sidenote…wish I could copy-paste that from the ‘about local’ popup)

  • What Operating System (OS) and OS version is being used?

MacOs Mojave - 10.14.6 (18G9323)

  • Attach the Local Log. See this Help Doc for instructions on how to do so:

Should not be relevant, please lmk if this is required

Security Reminder

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.

– This is why I didn’t attach my logs :wink:

Local-ssl-domainchange
Local-ssl-domainchange981×782 80.5 KB

Privacy_error
Privacy_error1027×676 121 KB

2

OK, so, it seems that I needed to shut down the entire localwp software after changing the domain name, in order for the ‘trust’ button to reappear for the new domain, not just restart the site as I did previously.

I am posting this for anyone else who has trouble with the SSL trust button being disabled after changing the domain name.

Suggestion for LocalWP - if you added a notice after changing a domain, in the green bar at the top, saying “You need to restart local to enable SSL on this site again” that would be a quick step to a way better UX in this case.

Hope this helps!

3

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