alex
Spent my Saturday evening and Sunday afternoon trying to migrate a multisite #WordPress from http to https. The plugin "Better Search and Replace" did not work. Installation of wp-cli into my Docker container running Apache/PHP was tedious, but after using `wp search-replace` I still got mixed-content errors and/or redirect loops. Turns out, letting the nginx reverse proxy handle https and still running WordPress itself on Apache with http (localhost) is the problem. 1/2
Apr 12 at 4:13pmWeb
Show threadalex20h ago
Read lots of HowTos and videos but all just suggested replacing http with https in the database only. Not sure how I came to the idea it's a reverse proxy problem, but #WordPress internally has an `is_ssl()` function and needs to be told https is always on. I still have to try this, but this very much sounds like the path forward. However this took me way too long to realize. Solution here: https://wordpress.stackexchange.com/a/387997/60025
Documentation here: https://developer.wordpress.org/advanced-administration/security/https/
Blog post will follow later. 2/2
How do I handle SSL properly when WP is behind a reverse proxy?

I am running Wordpress behind a proxy. The is_ssl() function in wp_includes/load.php will never be able to work in an environment like this because $_SERVER['HTTPS'] has no idea how the browser see...

WordPress Development Stack Exchange