error when delivering site over https

Hi,

That usually only happens in a couple of situations:

– You moved the site from http to https and didn’t clear the intermediate and normal cache on the settings (this plugin’s settings), or
– You have somehow overwritten the WP_HOME variable and therefore the one stored on the database is still in http format (did you do the necessary “search and replace” on the database?), or
– You’re behind a reverse proxy that is calling the site with http only, but serving it over https, or
– Your website is accessible both via http and https… in that case, whoever visits the page first will generate the static files with http … (I haven’t tested this, but if it happens it’s a bug and therefore I’ll fix it).

Go to your wp-admin > Settings > General, does it show as https?
If it does, then clear both caches on the plugin + any other caches you may be using (including on your reverse proxy, if you have it) + your browser cache.

Create a 301 redirect from http to https, this will ensure that all traffic falls on https and eliminate the duplicate content penalty on google.

Use the “Better Search and Replace” plugin to replace your site urls from http to https in all tables (backup first).

If none of these solve your problems, then let me know and I’ll happily see what else we can do.

Thankyou, that’s helpful.
Settings->general shows https://
I’ve cleared the cache.
and I’ve already fixed it on our site by forcing all traffic (except wp-admin) through http with a redirect.

Previously the site was accessible through https and http and was behaving weirdly, but your explanation for the files being built by the first visitor makes perfect sense.

it would be nice if I could serve the site by either http or https and for it to work correctly, so if it could be fixed in due course, I’d appreciate it.

Thanks

Great it’s solved.

I’ll take a look at the http vs https version, should be an easy fix.
I am pushing an update today so I’ll include this.

Thanks.

This update could not have come at a more perfect time. We just switched our site over to https yesterday and experienced the same problem. Clearing the cache did the trick, but it’s also nice to see there is now more compatibility for https!