Title: [Plugin: WordPress HTTPS (SSL)] Upgrade from 1.9.2 to 2.0.2 created redirect loop Last modified: August 20, 2016 --- # [Plugin: WordPress HTTPS (SSL)] Upgrade from 1.9.2 to 2.0.2 created redirect loop * Resolved [berchman](https://wordpress.org/support/users/berchman/) * (@berchman) * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-upgrade-from-192-to-202-created-redirect-loop/) * Hi Mvied, I updated from 1.9.2 to 2.0.2 and SSL is now completely broken. * Been running for an e-commerce website for months selectively securing specific pages and the plugin has worked wonders. * Today I updated to 2.0.2 and suddenly all the pages that were secure are now generating redirect loops. * I did uninstall 2.0.2, went into database and deleted all entries in the wp_options table that began with “wordpress-https” * I then hand installed 2.0.2 from a fresh download. Turned on and still the same errors. * Because this site uses some Facebook widgets there are calls to outside resources I have no way of encoding to https without this plugin. * I do have a private SSL certificate and also not sure what “port” to enter into the configuration field. * What should I do to make this work? * For now I have turned off the plugin. Let me know if you have any questions. Thanks, Bert * [http://wordpress.org/extend/plugins/wordpress-https/](http://wordpress.org/extend/plugins/wordpress-https/) Viewing 6 replies - 1 through 6 (of 6 total) * Thread Starter [berchman](https://wordpress.org/support/users/berchman/) * (@berchman) * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-upgrade-from-192-to-202-created-redirect-loop/#post-2421375) * More info. Here is the main homepage: [http://bit.ly/dDjM34](http://bit.ly/dDjM34) * Here is a secure page: [http://bit.ly/c6n3Ng](http://bit.ly/c6n3Ng) and one other: [http://bit.ly/v7ujkB](http://bit.ly/v7ujkB) * Let me know what you think. Thanks. * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-upgrade-from-192-to-202-created-redirect-loop/#post-2421664) * Hey Bert, * If you’re not using a custom port, you don’t need to put anything in the port field. * Would you mind if I took a look at it? I would just need an admin account with the ability to edit plugins so that I can try to identify what the problem is. It shouldn’t take me very long to figure it out. My email is mike[at]mvied[dot] com. * Thanks, Mike * Thread Starter [berchman](https://wordpress.org/support/users/berchman/) * (@berchman) * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-upgrade-from-192-to-202-created-redirect-loop/#post-2421671) * HI Mike, * I will send the access info to you shortly. For the benefit of everyone lets make sure we post the resolution here on the WordPress forums. * Thanks, Bert * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-upgrade-from-192-to-202-created-redirect-loop/#post-2421683) * Hey Bert, * The issue was that your server was sending back the HTTP_HOST variable with a port number on it. The plugin wasn’t expecting that. A slight modification fixed it right up. * You do have a partially encrypted error on the site being caused by [http://cdn.stumble-upon.com/i/badges/badgeRound65x18.png](http://cdn.stumble-upon.com/i/badges/badgeRound65x18.png) and [https://www.stumbleupon.com/badge/embed/2/?url=](https://www.stumbleupon.com/badge/embed/2/?url=). You may want to look into removing that button from your secure pages. * Also, I noticed that you manually set the Donate link to HTTPS. You don’t have to do that. Now that the plugin is functioning properly, you just need to check Force SSL on that page and it’ll fix links to that page for you. * Thanks, Mike * Thread Starter [berchman](https://wordpress.org/support/users/berchman/) * (@berchman) * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-upgrade-from-192-to-202-created-redirect-loop/#post-2421701) * Hi Mike, * Most excellent!!! 🙂 * I was able to go in and create a custom function that inserts the social plugin in all pages/posts NOT related to any e-commerce. * So all is well now. Green light in the browser with no warnings! * Really appreciate you taking the time to look and uncover the issue and hope that my particular issue helps contribute to the improvement of the plugin. * Cheers! Bert * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-upgrade-from-192-to-202-created-redirect-loop/#post-2421702) * Hey Bert, * It certainly has. It’s a bug that could definitely affect other users. Thank you! * Mike Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘[Plugin: WordPress HTTPS (SSL)] Upgrade from 1.9.2 to 2.0.2 created redirect loop’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/wordpress-https_bec2c9.svg) * [WordPress HTTPS (SSL)](https://wordpress.org/plugins/wordpress-https/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-https/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordpress-https/) * [Active Topics](https://wordpress.org/support/plugin/wordpress-https/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-https/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordpress-https/reviews/) * 6 replies * 2 participants * Last reply from: [mvied](https://wordpress.org/support/users/mvied/) * Last activity: [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-upgrade-from-192-to-202-created-redirect-loop/#post-2421702) * Status: resolved