- May 22, 2017 at 3:27 am #38121
I have 1 SSL Cert on a Root Domain but don’t have a wildcard SSL cert for the subdomains. I intend to just have https on the root domain (to secure Pro Sites/Stripe checkout) and keep all subdomains created with Pro Sites as regular http.
1) Install SSL Cert on Root Domain (exampledomain.com)
2) Install and enable WPMU Pro Sites
3) Install and enable Really Simple SSL on Root Domain (exampledomain.com)
4) Register a new subdomain site via Pro Sites (examplesubdomain.exampledomain.com)
– The automated wordpress new site registration email sent out on creation of the new subdomain site shows https://examplesubdomain.exampledomain.com instead of http. This causes the user to freak out when they get a “Your connection is not private” warning in Chrome when they click on the link
– When logged in as Network Admin and you click “Update Network” (https://example.com/wp-admin/network/upgrade.php) none of the subdomains are updated since wordpress prepends https to all subdomains.
Is there an easy way to force https just on the root domain and force http on all subdomains?May 22, 2017 at 8:42 am #38138
thanks for the feedback!
WordPress uses the home_url, site_url and get_admin_url functions to retrieve the various links. WordPress automatically assumes these should be https if the admin the user is logged in to is https. I see this as a bug in WordPress, because it doesn’t allow for non-https sites in a multisite environment. The get_admin_url is already filtered by Really Simple SSL to fix this, but we checked in the WordPress code, and it seems the site_url function is used to send emails.
We have developed a new function which should deal with this. The function checks if the home_url and site_url should be http or https when the plugin is enabled on a per-site basis. The function is implemented in version 2.5.17 which you can find on github: https://github.com/rlankhorst/really-simple-ssl. We are curious to hear if this solves your issue.
MarkMay 22, 2017 at 11:03 pm #38280
Hi Mark thanks for the quick reply and code commit. When do you anticipate having the official 2.5.17 release out? In the meantime I’ll look to spin up another test environment so I can test trunk.May 23, 2017 at 7:50 am #38299
we release a new version about once a month, the last release has been two weeks ago so the official release will be in roughly two weeks.
MarkJune 28, 2017 at 3:31 am #42170
Did this change get reverted in 2.5.18? It appeared to work correctly in 2.5.17, but after updating to 2.5.18, I can no longer update my subdomains.
1 SSL Cert on root domain and no certs on subdomains
– Log in as Network Admin
– Click “Update Network” (https://example.com/wp-admin/network/upgrade.php)
– Subdomains are updated
– None of the subdomains are updated since wordpress prepends https to all subdomainsJune 28, 2017 at 5:54 am #42176
Thanks for your input, you are right. I discovered that some lines that were uncommented in the last update in branch 2.5.18 on github, somehow haven’t merged with the commented out lines. As a result the commented out lines were left in the release code. This is the cause of your issue.
Apparently when the master has a commented out line, this is not merged when the new code is not commented out.
I have just released version 2.5.19, which should fix this. Let me know if that helps!September 14, 2018 at 11:36 pm #128633
can really simple plugin force http on my multisite subdomain, i’m using it but my emails are still https. pls helpSeptember 15, 2018 at 8:56 am #128707
Yes, Really Simple SSL can be used to activate SSL per site, leaving the rest on http.
Not sure what you mean with your emails being https?