Fix some common problems with insecure content on pages using SSL
Look in your web browser's error console.
NB: after you open your browser's console, refresh your page so that it tries to load the insecure content again and logs warnings to the error console.
You are probably loading content (such as images) with a URL that starts with "http:". Take that bit away, but leave the slashes, e.g.
//www.example.com/image.png; your browser will load the content, using SSL when your page uses it.
If your website is behind a load balancer or other reverse proxy, and WordPress doesn't know when SSL is being used, this plugin won't help. See my blog post, WordPress is_ssl() doesn’t work behind some load balancers, for some details. This plugin has a link to test whether is_ssl() is working, which you can find in the Tools menu in your WordPress admin. You might be able to fix it by adding this to your wp-config.php file:
// Amazon AWS Elastic Load Balancer, CloudFlare, and some others if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') $_SERVER['HTTPS']='on';
For websites hosted by Network Solutions, try downloading this gist and saving it into your plugins folder, then enable the plugin "Force SSL URL Scheme".
You are probably behind a reverse proxy -- see the FAQ above about load balancers / reverse proxies, and run the is_ssl() test from the WordPress admin Tools menu.
Post about it to the support forum, and be sure to include a link to the page. Posts without working links will be ignored.
Great! Tell me which plugin is yours and how to check for your new version, and I'll drop the "fix" from my next release.
Requires: 3.2.1 or higher
Compatible up to: 3.9.1
Last Updated: 2014-4-18
2 of 4 support threads in the last two months have been resolved.
Got something to say? Need help?