Title: Https redirection Affects all addon domains
Last modified: September 1, 2016

---

# Https redirection Affects all addon domains

 *  Resolved [Ike Ten](https://wordpress.org/support/users/ike-ten/)
 * (@ike-ten)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/https-redirection-affects-all-addon-domains/)
 * Hello [@rogierlankhorst](https://wordpress.org/support/users/rogierlankhorst/),
 * Thanks for this simple but effective plugin.
    It’s working nicely on my site 
   yet it affects all addon domains and tries to redirect them to https.
 * Since they are not on https they return an insecure and invalid ssl certificate
   error.
 * Can you kindly suggest how to limit it to just one domain; the main one in the
   root folder. Below is rule really simple ssl adds to my .htaccess file in my 
   root folder
 *     ```
       # BEGIN rlrssslReallySimpleSSL rsssl_version[2.3.8]
       <IfModule mod_rewrite.c>
       RewriteEngine on
       RewriteCond %{HTTP:X-Forwarded-Proto} !https
       RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
       </IfModule>
       # END rlrssslReallySimpleSSL
       ```
   
 * Thank you.
    Ike.
 * [https://wordpress.org/plugins/really-simple-ssl/](https://wordpress.org/plugins/really-simple-ssl/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Contributor [Rogier Lankhorst](https://wordpress.org/support/users/rogierlankhorst/)
 * (@rogierlankhorst)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/https-redirection-affects-all-addon-domains/#post-7593705)
 * I’ve just replied to your post on really-simple-ssl.com
 *  Thread Starter [Ike Ten](https://wordpress.org/support/users/ike-ten/)
 * (@ike-ten)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/https-redirection-affects-all-addon-domains/#post-7593713)
 * For anyone having a similar issues
    This is what worked for me. it also works
   for sub domains 1. Go to Really simple ssl settings and check **Stop editing 
   the .htaccess file**. save this setting. Alternatively you Add this line to your
   wp-config.php `define( 'RLRSSSL_DO_NOT_EDIT_HTACCESS' , TRUE );`.
 * They both do the same same thing; they stop Really simple ssl from editing the
   your .htaccess file henceforth.
 * 2. Now add Add the following conditions to the rewrites currently existing in
   your .htaccess, between the really simle ssl markers. Add them after the first
   ssl RewriteCond, but before the actual RewriteRule:
 *     ```
       RewriteCond %{HTTP_HOST} ^domain.com [OR]
       RewriteCond %{HTTP_HOST} ^www.domain.com
       ```
   
 * So your really simple ssl rule changes from this below
 *     ```
       # BEGIN rlrssslReallySimpleSSL rsssl_version[2.3.8]
       <IfModule mod_rewrite.c>
       RewriteEngine on
       RewriteCond %{HTTP:X-Forwarded-Proto} !https
       RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
       </IfModule>
       # END rlrssslReallySimpleSSL
       ```
   
 * to this below here.
 *     ```
       # BEGIN rlrssslReallySimpleSSL rsssl_version[2.3.8]
       <IfModule mod_rewrite.c>
       RewriteEngine on
       RewriteCond %{HTTP:X-Forwarded-Proto} !https
       RewriteCond %{HTTP_HOST} ^domain.com [OR]
       RewriteCond %{HTTP_HOST} ^www.domain.com
       RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
       </IfModule>
       # END rlrssslReallySimpleSSL
       ```
   
 * Where domain.com and [http://www.domain.com](http://www.domain.com) is the domain
   you still want ssl on.
 * Note your version number may be different the one here is at the time of writing
   this.
 * Refer to this post [here](https://wordpress.org/support/topic/subdomain-conflict?replies=4#post-7473538)
   for a similar issue and solution.
 * Credits to Rogier Lankhorst ( [@rogierlankhorst](https://wordpress.org/support/users/rogierlankhorst/))
   for coming up with this fix.
 *  [Marty](https://wordpress.org/support/users/bozzmedia/)
 * (@bozzmedia)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/https-redirection-affects-all-addon-domains/#post-7593834)
 * Just wanted to say MAJOR THANKS for sharing the solution, came in handy today.
   I would suggest adding this to the documentation. Cheers.
 *  Plugin Contributor [Rogier Lankhorst](https://wordpress.org/support/users/rogierlankhorst/)
 * (@rogierlankhorst)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/https-redirection-affects-all-addon-domains/#post-7593835)
 * Good to hear. I’ve added it as an article to the documentation.
 *  [namgostar](https://wordpress.org/support/users/namgostar/)
 * (@namgostar)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/https-redirection-affects-all-addon-domains/#post-8134795)
 * Hi Rogier,
 * I have followed the instructions above and [here](https://really-simple-ssl.com/knowledge-base/preventing-subdomains-add-domains-getting-forced-https/).
   However, it is not working for me. It is continuing to add the ‘s’ to the staging
   site, and even when I try to delete it from the url, it keeps putting it back.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Https redirection Affects all addon domains’ is closed to new replies.

 * ![](https://ps.w.org/really-simple-ssl/assets/icon-256x256.png?rev=2839720)
 * [Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)](https://wordpress.org/plugins/really-simple-ssl/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/really-simple-ssl/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/really-simple-ssl/)
 * [Active Topics](https://wordpress.org/support/plugin/really-simple-ssl/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/really-simple-ssl/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/really-simple-ssl/reviews/)

## Tags

 * [addon](https://wordpress.org/support/topic-tag/addon/)
 * [sub-domains](https://wordpress.org/support/topic-tag/sub-domains/)

 * 5 replies
 * 4 participants
 * Last reply from: [namgostar](https://wordpress.org/support/users/namgostar/)
 * Last activity: [9 years, 8 months ago](https://wordpress.org/support/topic/https-redirection-affects-all-addon-domains/#post-8134795)
 * Status: resolved