Just curious if you have any advice for multisite

Thanks for your feedback, would be nice to get this working as well. Do you use WordPress MU Domain Mapping plugin? If so, I’ll take a look at the way this plugin handles the redirection to see if I can come up with a solution.

Could you send me a text file with your .htaccess rules as well? To info@

In the meantime, could you try to set the .htaccess file to not writable, and then log in to the admin again? The really simple ssl plugin will then also add some JavaScript which forces to https. Let me know how that works for you, I’ll get back to you as soon as I have looked into this.

I am using the WordPress MU Domain Mapping plugin.

The htaccess trick did work, so I will mark this resolved, but I guess I would like to see the ultimate solution, as security plugins like to write to htaccess.

Thanks for the quick response.

Since the last update, the javascript redirect is added by default. So you can set your .htaccess to writable again, and it should work.

One suggestion that I might make regarding multisite – can you make it so that each site can activate or deactivate the plugin?

I bought a multi-domain cert for 3 domains, but I am going to use many more domains than 3. I guess I would like to be able to not have https on for those sites that aren’t in the cert.

No worries if not, just an idea.

Thanks for your suggestion, a great idea! I just did some tests on a WPMU multisite install, and it seems everything is working fine, only the .htaccess rewrite rules have to be adapted to make it working for multisite.

I will make an update where, in case of a per-site install, the rewrite rule will work only on the site where the plugin is activated.

If you add
define( 'RLRSSSL_DO_NOT_EDIT_HTACCESS' , TRUE );
to your wp-config.php, and remove the really simple ssl rewrite rules from your htaccess, it should work already on a per-site basis, as the javascript redirect will take care of the redirect.

THANK YOU for a simple plug-in that solves a whole heap of security issues.

I am just looking for a little clarity. Even after the update two weeks ago, if I make the alterations you describe above will I stop getting “cannot verify identity” warnings on all but the main site? I have one cert and a server with a dedicated IP.

You mean when some sites are not ssl? If you disable the htaccess edits your other sites should be fine. The per site activation with .htaccess is not possible yet. My priority has been on fixing all possible configurations in server setups. But within a couple of weeks I’ll publish an update with per site activation for subdomain setups. Combination with domain mapping will follow later.

For anyone interested in wpmu per site install, I’ve just released a betaversion for wordpress multisite where it is possible to activate per site. Download beta here.

Backup at least the wp-config.php, .htaccess and the old plugin files before you install.

Any feedback is welcome.

I’ve installed and activated this beta. I have half a dozen http domains, and now two https domains. Everything is working great!

Since the 2.2.1 beta worked, I deleted it and installed the latest version (2.2.8). No change, all domains are still working. Sites that should be SSL are, and those that should allow regular http do.

Thanks so much for all of your work on this plugin!

Edit – in case it helps somehow, here are a couple of the domains:
https://specficmedia.com
https://vividmuse.com

Hello @rogierlankhorst

Thanks for the plugin and I will be donating, but need to get multisite handled and cleared up.

https://www.ads-software.com/plugins/really-simple-ssl/faq/ (In the current version in the WP repository is the below still needed to make it work for installing per site on WordPress MULTISITE? I have subdomain too FYI. I notice in the FAQ section near the bottom it does not reference this like it does in this thread for steps to take to assure it works? Is it built-in now or do these steps still apply in the current version to be sure it works?

You mentioned in this thread this:
Thanks for your suggestion, a great idea! I just did some tests on a WPMU multisite install, and it seems everything is working fine, only the .htaccess rewrite rules have to be adapted to make it working for multisite.

I will make an update where, in case of a per-site install, the rewrite rule will work only on the site where the plugin is activated.

If you add
define( ‘RLRSSSL_DO_NOT_EDIT_HTACCESS’ , TRUE );
to your wp-config.php, and remove the really simple ssl rewrite rules from your htaccess, it should work already on a per-site basis, as the javascript redirect will take care of the redirect.

In other words, do I need to edit .htaccess or wp-config at all to get this to work on multisite subsites on a per subsite basis OR have you taken care of all that too in this latest release (any extra steps needed now for WordPress MULTISITE subdomain per subsite installs NOT network activated)?

I am just trying to be sure I understand and have my basis covered . . . smile.

Greg

P.S. IF there are extra steps to be sure it works right for folks like us, then you may want to append that section in the FAQ to include anything for MULTISITE folks to do. IF not, then of course, you are all good.

Any extra precautions still needed like backing up the .htaccess, wp-config or anything at all? More info in the FAQ would be great if anything at all is needed for MULTISITE folks so they know 100% (reason I say this is because I know your update to accommodate this is fairly new).

??

Those things I mentioned here should not be necessary anymore. The plugin is multisite ready. In the current “stable” version a bug was discovered concerning multisite, which applies if you activate websites after activating the plugin. This is solved in the current beta: https://downloads.www.ads-software.com/plugin/really-simple-ssl.zip

@rogierlankhorst

Cool on the zip. Does the release you put out cover that zip in your last post? I am sure . . . yes (but just checking):

https://screencast.com/t/kRg0vtv1Vgwq

?

There was an issue with 2.2.13, I quickly had to fix it, so the other issue is not fixed yet. I’m planning to release 2.2.16 today, which has the intended multisite fix.