Title: WordFence blocking http/https redirect
Last modified: March 21, 2023

---

# WordFence blocking http/https redirect

 *  Resolved [DJ](https://wordpress.org/support/users/itsjustdj/)
 * (@itsjustdj)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/wordfence-blocking-http-https-redirect/)
 * When I have WordFence activated, it’s blocking the redirect from non-secure http
   to secure https. When I deactivate the plugin, it works fine. I’m also running
   ReallySimple SSL.
 * Before you ask, I have the URLs set to https:// in WordPress settings.
 * Is there a setting in WordFence to fix this?

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

 *  Plugin Support [wfpeter](https://wordpress.org/support/users/wfpeter/)
 * (@wfpeter)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/wordfence-blocking-http-https-redirect/#post-16584179)
 * Hi [@itsjustdj](https://wordpress.org/support/users/itsjustdj/), thanks for getting
   in touch.
 * Are you seeing actual Wordfence-branded block pages from the very start of making
   requests to your site URL, or only when following links, or under another situation?
 * I’m not sure if you’re depending on Cloudflare for SSL to work, or are on another
   server configuration so it might be a good idea to send over a diagnostic report.
   There can be other issues with how SSL on your server, or the Really Simple SSL
   plugin is handled but it’d be hard to say with the information I have.
 * You can send us the diagnostic report to **wftest @ wordfence . com**. The link
   to do so appears at the top of the **Wordfence > Tools > Diagnostics** page. 
   Then click on **“Send Report by Email”**. Please add your forum username where
   indicated and _respond here after you have sent it._
 * **NOTE:** It should look as follows – Screenshot of [Tools > Diagnostic > Send by Email](https://www.wordfence.com/wp-content/uploads/2021/09/diagnosticsendbyemail.png)
 * Thanks,
   Peter.
 *  [tpipta](https://wordpress.org/support/users/tpipta/)
 * (@tpipta)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/wordfence-blocking-http-https-redirect/#post-16845215)
 * Just curious if there was resolution to this? I’m experiencing the same scenario.
   It’s directly related the to the rate limiting function for us. Regardless of
   the settings, it will block redirect.
    -  This reply was modified 2 years, 11 months ago by [tpipta](https://wordpress.org/support/users/tpipta/).
 *  Thread Starter [DJ](https://wordpress.org/support/users/itsjustdj/)
 * (@itsjustdj)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/wordfence-blocking-http-https-redirect/#post-16845609)
 * Hey [@tpipta](https://wordpress.org/support/users/tpipta/) and [@wfpeter](https://wordpress.org/support/users/wfpeter/),
 * I apologize for not coming back to comment on the resolution sooner. It turns
   out it was a combined issue with the Really Simple SSL configuration and the 
   web host. WordFence wasn’t causing any issues.

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

The topic ‘WordFence blocking http/https redirect’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [HTTPS](https://wordpress.org/support/topic-tag/https/)
 * [redirect](https://wordpress.org/support/topic-tag/redirect/)
 * [SSL](https://wordpress.org/support/topic-tag/ssl/)

 * 3 replies
 * 3 participants
 * Last reply from: [DJ](https://wordpress.org/support/users/itsjustdj/)
 * Last activity: [2 years, 11 months ago](https://wordpress.org/support/topic/wordfence-blocking-http-https-redirect/#post-16845609)
 * Status: resolved