This method says that it cannot find my server. I used http://www.mysite.com/wp-content/plugins/really-simple-ssl/force-deactivate.php and https which says not secure….
https://really-simple-ssl.com/knowledge-base/uninstall-websitebackend-not-accessible/
Why wouldn’t just deleting that folder be safe?
After renaming the plugin file in my ftp and delete browser history, the site shows but I can’t access the backend to delete it from there.
There is nothing from the plugin in my .htaccess, wp-config, not theme function’s file to remove. https://really-simple-ssl.com/knowledge-base/when-the-built-in-deactivation-does-not-work-manual-uninstalling/
I tried http://www.mysite.com/wp-content/plugins/really-simple-ssl/force-deactivate.php again and it keeps going to https. I’ve emptied my cache specifically. https://oit.colorado.edu/tutorial/clear-web-browser-cache-safari-6.
Before going into my database https://ww.wp.xz.cn/support/article/changing-the-site-url/, I just deleted the folder, refreshed, emptied the cache and my admin is still down.
I will just ask my host to restore the site from 24 hrs ago.
My host restored the entire site and I still cannot access and admin.
If your hoster restored the old version of your site, and you still can’t access the admin, the redirect to https is probably still in your browser cache. I would recommend to try your site with a different browser, or using an anonymous window.
Based on the error you saw, “can’t establish a secure connection”, this means you don’t have a valid SSL certificate. You can contact your hosting company to install valid SSL certificate.
Really Simple SSL requires a valid SSL certificate. You can check your certificate here: https://ssllabs.com/ssltest
See this article for more information on certificates:
https://really-simple-ssl.com/knowledge-base/installing-an-ssl-certificate/
I had emptied the cache numerous times. Closed safari, and turned off the comp. I wouldn’t have done this on activation if it didn’t recognize the cert. I had a cert which it recognized. Perhaps I needed the mix setting selected to avoid all this? Or maybe it shouldn’t be recommended for multisite and subdomains.
If someone has to go into their sql database to remove this, that’s subpar.
@functionmunchkin you don’t need to go into the database to remove this, you can use the deactivate script:
https://really-simple-ssl.com/knowledge-base/uninstall-websitebackend-not-accessible/
But as your host restored the old version, there’s nothing to remove: your site was already restored to the original situation. This means that anything that’s redirecting to https, is coming from your own computer. You can also try a different machine.
It will work fine on multisite, but a valid SSL certificate is required. It sounds as if the quickest way to resolve it is to ask your hosting company to install a valid SSL certificate. Then Really Simple SSL will start working and you can access your site over https.
“ I wouldn’t have done this on activation if it didn’t recognize the cert.“ It clearly had one in order to allow me to continue to the next steps. I explained above that I used your backend method (posted the exact same link) which didn’t work and had to try the extra two suggestions by your site. Even my host didn’t want to meddle with the database.
Changing The Site URL
Anyway. This might be a browser issue besides the cache. Safari desktop.
Plugin Author
Mark
(@markwolters)
Hi Stacy,
can you provide us with your site address so we can have a look?
I believe this is a safari desktop 10.1.2 problem. I’m also using multisite. The plugin was removed since the site was restored. bit.ly/3cgLH3D
It looks like your site force redirects all requests to http. This will cause an issue when you activate https: if the site is redirected to https, then redirected back to http by your custom force redirection, a loop might occur.
To prevent future issues I would recommend to remove the force redirect. It may be located in your .htaccess file, or in a redirection plugin.
I’m not having a redirect issue as I’m still on the https when I visit it. I tested deactivating all plugins already. What other mentions in the .htaccess would I be looking for besides what your plugin was supposed to add?
I can only try reinstalling your plugin after deactivating all others but I don’t think it’s worth the risk of having to pay my host to restore again. The only redirect plugin I have activated is Sky Login Redirect which Redirects users to the page they were reading just before logging in. Also redirects to homepage when logging out.
My host confirmed that there is no force redirect to http. But I am now getting forced redirect on all subs to https after regrettably trying your suggested plugin again with them and now they want to charge me to restore. Even after it’s deleted, I am locked out again.
I notice the subdomains of your site do not have a valid SSL certificate. It looks like you have a certificate which is only valid for the main domain, but not for the subdomains. You need a wildcard certificate to cover the subdomains.
The .htaccess redirect is only enabled if you explicitly enabled the setting “301 htaccess redirect”. If you did not enable it, no changes will have been made to the .htaccess file.
By default, only the site_url and home_url are changed to https. You can change them back in the database, but I would recommend to use the force deactivation script, which reverts all changes on all sub-sites.
You can find the instructions to use it here:
https://really-simple-ssl.com/knowledge-base/uninstall-websitebackend-not-accessible/
After running it, you may need to clear your browser cache.
I mentioned above that the deactivation script didn’t work the first time. Unless I have to try the database part of it now. Network activating causes sub lockout before enabling any setting.
This shouldn’t offer network activation if there’s a “domains not matched” ssl error.
Force https should be a setting and not automatic. There’s already a manual one. I will try taking their rewrite for https out. As well as
define(‘FORCE_SSL_ADMIN’, true); in wp.config.
^This line allows WordPress to force SSL / HTTPs in WordPress admin area. It also works on WordPress multisite networks.
https://www.wpbeginner.com/wp-tutorials/how-to-add-ssl-and-https-in-wordpress/
When attempting http on the subs, Chrome is actually telling me that they can’t even be found..
Using the exemption on firefox shows 404.
Adding a subdomain to subdomains in cpanel shows the index pg only.
They’re gone…
I would’ve checked the subs own theme function files to see if adding this would work. update_option( ‘siteurl’, ‘http://example.com’ );
update_option( ‘home’, ‘http://example.com’ );
How would doing this again in the config file affect the subs?
Changing The Site URL
