The button “WP Admin” opens in http rather than https, even though I have trusted SSL.
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
Create a brand new, empty site in local. Note: my default extension is localwp.
Trust the domain, so the aim is for all urls to use https.
In WordPress (“/wp-admin/options-general.php”), set the site url and home url as “https://…”.
Go back to localwp, click on the WP Admin button. It sends a request to an http page, namely “/wp-admin/?localwp_auto_login=1”, which then redirects to an https page, namely “/wp-admin/user/”, which then redirects to the standard WP login page.
If you manually try the WP Admin url as an https instead (“/wp-admin/?localwp_auto_login=1”), it works.
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.
Actually, I’ve got another issue related to this, which probably needs to be sorted first, although I assume it’s connected to the same underlying problem.
When I turn on one-click admin, I don’t get a list of admin users to select from. When I click on the drop down icon, it pauses briefly and then shows nothing.
We have a Windows Troubleshooting guide below that goes over some common items worth checking first. For example, make sure you’re running Local as an admin user, that you don’t have any security blockers, and that Local has access to update your Hosts file.
After that we have some additional SSL troubleshooting steps here:
Keep us posted if problems persist or if you have any other questions!
The new test sites I am creating do not seem to have a local-site.json file, whereas my existing sites do. Has something changed recently in localwp to move from a json file to an internal db now?
Good catch @billinghamn! Sorry I didn’t see that one. It is in fact still an open bug that hasn’t been resolved yet. I can check in with our dev team for an update.
I checked with our Local Developers and confirmed that this one is still on their radar, and they will be taking a closer look at it soon. It turned out to be trickier to resolve, as some complexities arose after initially investigating it. Thank you for your patience and communication with us on this @billinghamn.