Using a reverse proxy to provide a secure connection to a WordPress site
What’s a reverse proxy? well, in this context, wikipedia has this to say:
In computer networks, a reverse proxy is a type of proxy server that retrieves resources on behalf of a client from one or more servers.
In the case of secure websites, a web server may not perform SSL encryption itself, but instead offloads the task to a reverse proxy that may be equipped with SSL acceleration hardware. — https://en.wikipedia.org/wiki/Reverse_proxy
it’s an example of the above. in oversimplified terms i guess. maybe. — me
A guide (read: a reminder for myself)
- the A records for both domain names example.com and www.example.com need to point to the IP address provided by sucuri in order for them to be able to generate and install a valid LE cert for the domain
- once that is done, select Partial HTTPS under the HTTPS/SSL tab. Partial SSL because sucuri is reverse proxying to a non-https server. Full HTTPS is for when the hosting server already has an SSL cert installed - then it’s an https-to-https connection all the way.
- Next up include the code below in your wp-config.php file to prevent the site from going into an infinite redirect loop. Read up more on this here: https://codex.wordpress.org/Administration_Over_SSL
/* Handle HTTPS Protocol */ if ($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') $_SERVER['HTTPS']='on';
- change site and home url protocols to https
- lastly, your site will most likely still have some resources being loaded over insecure http. hunt these down and deeeestroy them. just kidding, just search & replace absolute urls with relatives ones where you can. if some http resources still remain after that, figure it out son.
While playing around with Content Security Policy I stumbled upon the directive
upgrade-insecure-requests which tells a browser or user agent to load any resources with HTTP URLS over HTTPS instead. This directive is intended for sites that have a large number of HTTP URLs that would otherwise need to be re-written by hand.
So instead of re-writing all those pesky insecure URLs by hand as suggested by an older version of myself, if possible, just use the CSP directive by adding it to your site’s headers or by adding the below meta tag to your
<!-- meta tag in the head --> <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests" />
Did you win?
yes? good! now it’s time feel good about yourself for completing this simple task by watching this video ✌️
- Troubleshooting Mixed Content Warnings with HTTPS - https://blog.sucuri.net/2016/04/troubleshooting-mixed-content-warnings-https.html
- How to Install an SSL Certificate - https://sucuri.net/guides/how-to-install-ssl-certificate
- CSP: upgrade-insecure-requests - https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/upgrade-insecure-requests