Conversation
supportHello, I am trying to uninstall this plugin but when I do it crashes the entire website. Can you please advise on what I should do to remove it safely. I have the following enabled: Fix insecure content = Content. Fixes for specific plugins and themes = WooCommerce + Google Chrome HTTP_HTTPS bug (fixed in WooCommerce v2.3.13). Ignore external sites = no enabled. HTTPS detection = uable to detect HTTPS. I did not originally implement this plugin so when I go to change HTTPS Detection to HTTP_X_FORWARDED_PROTO or even standard WordPress function, it also crashes the site. I would appreciate any help you can give!
G’day adequatelyadept, The setting “unable to detect HTTPS” is the most problematic setting when removing the plugin. It forces detection of HTTPS whenever the site URL is set to HTTPS. Deactivating the plugin will stop that happening, and your website will enter a redirection endless loop. When you visit the settings page for this plugin, what is the recommended setting for HTTPS detection? If it’s the setting you’re on, then your website can’t easily tell when pages are loaded by HTTPS, which is why this plugin has been used. If it’s another setting, then there’s a way to remove this plugin by adding some code to your wp-config.php file. Another thing you can look at is the array of environment variables that you get when you run the admin page: Tools > SSL Tests With luck, it will give some way to detect when your pages are loaded from HTTPS. cheers, Ross
Hi Ross, Previously it was saying “HTTP_X_FORWARDED_PROTO (e.g. load balancer, reverse proxy, NginX)” was the recommended option but that isn’t appearing anymore for some reason. As for SSL test, it shows the following: error <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access this resource.</p> </body></html> Regards, Karl
G’day adequatelyadept, Your site security settings may be blocking execution of scripts directly in plugin folders, so the plugin isn’t able to show you a recommended method for detecting HTTPS on your website. Please contact me via my support form , and we can talk privately about how to get that information, i.e. without exposing details of your site publicly. cheers, Ross
G’day adequatelyadept, The setting “unable to detect HTTPS” is the most problematic setting when removing the plugin. It forces detection of HTTPS whenever the site URL is set to HTTPS. Deactivating the plugin will stop that happening, and your website will enter a redirection endless loop. When you visit the settings page for this plugin, what is the recommended setting for HTTPS detection? If it’s the setting you’re on, then your website can’t easily tell when pages are loaded by HTTPS, which is why this plugin has been used. If it’s another setting, then there’s a way to remove this plugin by adding some code to your wp-config.php file. Another thing you can look at is the array of environment variables that you get when you run the admin page: Tools > SSL Tests With luck, it will give some way to detect when your pages are loaded from HTTPS. cheers, Ross
Hi Ross, Previously it was saying “HTTP_X_FORWARDED_PROTO (e.g. load balancer, reverse proxy, NginX)” was the recommended option but that isn’t appearing anymore for some reason. As for SSL test, it shows the following: error <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access this resource.</p> </body></html> Regards, Karl
G’day adequatelyadept, Your site security settings may be blocking execution of scripts directly in plugin folders, so the plugin isn’t able to show you a recommended method for detecting HTTPS on your website. Please contact me via my support form , and we can talk privately about how to get that information, i.e. without exposing details of your site publicly. cheers, Ross