I wonder if there is still some caching on your network.
There are some different things to try and get around network caching. Restarting your device, restarting the network router/modem, using a VPN connection, or adding a cache-breaking path to the end of the site that’s cached. Adding /? followed by any 4 random characters (/?1234 for example) will sometimes break the cache as well.
Hey Nick, I just changed the Local Settings to use Firefox (first) and then Safari. I haven’t previously opened the site with either! Both browsers opened the HTTP url for the site. I thought maybe it was a Chrome thing as it can exhibit some stubborn caching traits, but it’s obviously not limited to Chrome.
So I reset the settings back to using Chrome; quit Local, deleted all of the cookies and site data for the site URL and quit Chrome. Restarted my MacBook, started Local and clicked Open Site; same behaviour!!
I have a Chrome Extension to show me any redirect paths for sites visited and there are no redirects for this URL; Local is opening the HTTP version of the site every time.
I searched the DB again for any instances of HTTP: and pingomatic is the only one.
I’ve performed countless HTTP to HTTPS migrations over the years and often use HTTPS Checker to provide a visual confirmation of a site’s status post-migration. I dropped the SiteURL into the App =>
What I don’t understand is what URL is Local “calling” when I use the Open Site button below and where is it coming from??
Hmm, that is pretty odd behavior. Regardless of how Local opens the site http:// or https:// I would expect that you’d be redirected to https:// anyway.
If you create a brand new Local site and set up SSL, trust, etc does it work?
Select the site and I can see that the certificate is now trusted.
Click “Open Site”…
What am I missing?
PS: Probably unrelated, but I still have Desktop Server installed, and it’s recently stopped working after installing Local… Can no longer access Localhost!
I was hoping to export my sites from DS and import them into Local, but one issue at a time…
I have tried changing the default browser settings in Local and opening the sites in Safari and Firefox => Same Result! Neither browser had opened the site previously so there was no stored cookies / site data / cache.
Yes, I had already discovered that the one-click “Trust” button does not work. I gather that due to the issues with newer Mac OS not allowing Local to trust SSL certificates automatically, that I have to manually trust the certificate for every site via “Key Chain Access”…
a) I have done this for both sites
b) I have changed the Site URLs and Home URLs to https://
c) I have run a search/replace over the DBs and replaced all instances of http with https
Below are the details for the two sites I have installed - Local is clearly showing that the certificates are both “trusted"
