Title: https conversion
Last modified: August 22, 2016

---

# https conversion

 *  Resolved [animagic](https://wordpress.org/support/users/animagic/)
 * (@animagic)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/https-conversion/)
 * Are there any specific changes or recommendations for settings within the plugin
   that should be made before attempting to switch to [https://](https://wordpress.org/support/topic/https-conversion/?output_format=md).
   I have attempted everything short of uninstalling the few plugins I have and 
   reverting the database to a clean version with no plugin data. Currently, even
   with the Rename login feature and the Cookie rename feature turned off, I lose
   access to wp-login.php after switching the WordPress URL Settings to [https://](https://wordpress.org/support/topic/https-conversion/?output_format=md).
   I also get an endless loop when attempting to place a rewrite rule for 301 redirect
   to [https://](https://wordpress.org/support/topic/https-conversion/?output_format=md).
 * I am guessing this is an htaccess issue with the myriad of rules placed in it
   by AIO Security. I love the plugin but am having some serious issues with converting
   to https://
 * For reference, I have a live site at [http://mysite.com](http://mysite.com) and
   a development site at [http://dev.mysite.com](http://dev.mysite.com) BUT the 
   development site has its own directory and is not a true sub-domain/sub-directory
   of the main site.
 * [https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/)

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

 *  Plugin Contributor [mbrsolution](https://wordpress.org/support/users/mbrsolution/)
 * (@mbrsolution)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/https-conversion/#post-5560593)
 * Hi animagic are you sure you have set up the backend correctly to [https://](https://wordpress.org/support/topic/https-conversion/?output_format=md)?
 * Can you share what areas you have changed in the backend to [https://](https://wordpress.org/support/topic/https-conversion/?output_format=md)?
 * Thank you
 *  Thread Starter [animagic](https://wordpress.org/support/users/animagic/)
 * (@animagic)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/https-conversion/#post-5560722)
 * I found it was not an issue with the plugin. My pair of web servers are behind
   a Load Balancer that our host runs and the LB was not setup properly to send 
   the X-Forwarded-Proto header. All is well now!
 *  Plugin Contributor [mbrsolution](https://wordpress.org/support/users/mbrsolution/)
 * (@mbrsolution)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/https-conversion/#post-5560723)
 * Hi animagic I am glad to hear 😉
 * Can you mark this support thread as resolved.
 * Thank you
 *  Thread Starter [animagic](https://wordpress.org/support/users/animagic/)
 * (@animagic)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/https-conversion/#post-5560739)
 * Resolved
 *  Thread Starter [animagic](https://wordpress.org/support/users/animagic/)
 * (@animagic)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/https-conversion/#post-5560762)
 * Reopening the ticket.
 * This is a side-issue that possibly pertains to my conversion to [https://](https://wordpress.org/support/topic/https-conversion/?output_format=md).
 * I have 2 sites, 1 live and 1 dev. the dev site has been successfully flipped 
   to https:// but in doing so, either I edited some code or the database in some
   fashion so that the Cookie Based Brute Force Protection does not correctly redirect
   attempts at /wp-login.php to my current redirect of [http://127.0.0.1](http://127.0.0.1).
   It still provides the login page at /?mysecretword=1 thought which is odd. My
   live site is not https:// yet as we have not finished testing the theme, etc.
   on the dev site and the redirect works correctly there.
 * I have edited the htaccess file in the dev site to reflect the change to https
   in the Cookie BF section and it is identical to the live site’s htaccess in all
   other regards. I also don’t see any anomalies or differences in the database,
   thought I may be missing something.
 * Any thoughts?

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

The topic ‘https conversion’ is closed to new replies.

 * ![](https://ps.w.org/all-in-one-wp-security-and-firewall/assets/icon-256x256.
   png?rev=2798307)
 * [All-In-One Security (AIOS) – Security and Firewall](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/)
 * [Active Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/reviews/)

## Tags

 * [htaccess](https://wordpress.org/support/topic-tag/htaccess/)
 * [HTTP](https://wordpress.org/support/topic-tag/http/)
 * [HTTPS](https://wordpress.org/support/topic-tag/https/)

 * 5 replies
 * 2 participants
 * Last reply from: [animagic](https://wordpress.org/support/users/animagic/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/https-conversion/#post-5560762)
 * Status: resolved