Wordfence + Cloudflare : 307 Temporary Redirect

  • Resolved jodes01

    (@jodes01)


    5 years, 2 months ago

    Hello !

    I have some probleme on twho website who run cloudflare with Wordfence.
    I can’t scan because the diagnostic say :

    wp_remote_post() test back to this server failed! Response was: 307 Temporary Redirect
This additional info may help you diagnose the issue. The response headers we received were:

HTTP/1.1 307 Temporary Redirect
Date: Tue, 23 Mar 2021 19:01:53 GMT
Content-Type: application/octet-stream
Transfer-Encoding: chunked
Connection: close
Set-Cookie: __cfduid=d1ee303c6d53af5eb2d80070c3b6e8ee81616526113; expires=Thu, 22-Apr-21 19:01:53 GMT; path=/; domain=.natureacoeur.fr; HttpOnly; SameSite=Lax; Secure
cache-control: private, max-age=0, no-cache
expires: Mon, 01 Jan 2000 01:01:42 GMT
Set-Cookie: o2s-chl=62a24be25479320360d075676bb949ca63891513c5cc12c6f5ed89e310f40aa9; path=/
CF-Cache-Status: DYNAMIC
cf-request-id: 090210120900002774e31d4000000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=yMt3Cjgdqfm79bw37cp9PtRIwnZstYO3morh2cBK8rzMJIwwrZ4pEWzFW8RVnjpqFGIGRPKioNN%2ByAVSAIbEJhy1F3mIhQ7M0e6sLYYaNMY%3D"}],"max_age":604800,"group":"cf-nel"}
NEL: {"max_age":604800,"report_to":"cf-nel"}
Strict-Transport-Security: max-age=15552000; includeSubDomains; preload
X-Content-Type-Options: nosniff
Server: cloudflare
CF-RAY: 6349e930098f2774-PRG
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400

    I have try some solution…
    Add worfence ip on cloudflare, delete headers protection, add ip cloudflare in wordfence…
    Nothing works.

    What can i do ?

    thanks !

    • This topic was modified 5 years, 2 months ago by jodes01.
    • This topic was modified 5 years, 2 months ago by jodes01.
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support WFAdam

    (@wfadam)

    5 years, 2 months ago

    Hello @jodes01 and thanks for reaching out to us!

    If your site is protected by Cloudflare, you may need to update your Cloudflare settings to allow your site to connect back to itself. You should be able to do this by going to your Cloudflare control panel. You mentioned you added the Wordfence IP but you will need to add your site’s actual IP.

    • Login to Cloudflare
    • Go to “Firewall”
    • Click the “Firewall Rules” tab
    • Click “Create a Firewall rule”
    • Name the rule under “Rule Name”
    • Set the “Field” under “When incoming requests match…” to “IP Address”
    • Enter your site’s IP address under “Value”
    • At the bottom, under “Then…Choose an action” change “Block” to “Allow”
    • Click “Deploy

    Let me know if this helps and if you have any questions!

    Thanks again!

    Thread Starter jodes01

    (@jodes01)

    5 years, 2 months ago

    Hi and thanks you for your response !
    Unfortunately this does not work.
    As said in my post above, I have already tried.
    I tried to us with the server ip, the site ip as well as another ip displayed in the line IP (s) used by this server diagnostic but it doesn’t change anything: ‘(
    This 3 IP are registered with “OR” rule in the cloudflare firewall.

    I have Wordfence premium for this 2 websites.

    I have checked :
    Start all scans remotely (Try this if your scans aren’t starting and your site is publicly accessible)

    I’hve tested with Security Level in Essentialy off on cloudflare, unchecked all firewall option in this and nothing is working 🙁

    • This reply was modified 5 years, 2 months ago by jodes01.
    Plugin Support WFAdam

    (@wfadam)

    5 years, 2 months ago

    It’s definitely something from Cloudflare blocking the requests as the error mentions it directly. Can you screenshot the whitelist in Cloudflare for me to review with the IPs blocked out, since this is public.

    Can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so 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.

    Thanks again!

    Thread Starter jodes01

    (@jodes01)

    5 years, 2 months ago

    Hello, I sent all the information needed 3 days ago.
    Did you receive them well?

    thanks 🙂

    Plugin Support WFAdam

    (@wfadam)

    5 years, 2 months ago

    Yes! Sorry for the late reply!

    I think it’s Cloudflare still as the redirect lands on a Cloudflare block page. Its possible the IP entered is incorrect in the Cloudflare Whitelist.

    Double-Check if you entered the first IP shown under IP(s) used by this server in the Diagnostics report that he sent.

    Also, if you have Cloudflare’s “under attack” mode enabled too, you could try temporarily disabling that. It’s meant to block automated connections and could be related.

    Let me know what you find!

    Thanks again!

    Thread Starter jodes01

    (@jodes01)

    5 years, 2 months ago

    Hi !
    I’ve all checked, and it’s all OK for the cloudFlare configuration.
    I’ve added the website custom IP (with ipXtender) and all the ip detected by wordfence.
    I have send you and other report with cloudFlare offline, and you can see “OK xxx.xxx.xxx.xxx”, that’s the custom IP.
    But it’s already accepted from the start with all other IP.
    I really don’t understand this !
    Sometimes, Wordfence say the Header configuration is not good too, but it’s on Cloudflare “CF-Connecting-IP”, and the ip detected is good…

    Thanks

    Thread Starter jodes01

    (@jodes01)

    5 years, 2 months ago

    I have test with :
    Use the X-Real-IP HTTP header. Only use if you have a front-end proxy or spoofing may result.

    And the scan is running, but IP’s detected by Wordfence aren’t good…

    And with : Cloudflare “CF-Connecting-IP”, i have “Configured but not valid”.
    I don’t understand, CloudFlare is running on this website :/

    I have find it,
    on an other website with Custom website IP, it’s the same problem.
    I have stopped this custom ip and use the IP server, and it’s running good !

    But, i can’t change the custom IP for this for multiple reason.
    Can you find a solution for wordfence detect the real good site IP and not the server IP ? I think’s it’s a start of solution !

    • This reply was modified 5 years, 2 months ago by jodes01.
    • This reply was modified 5 years, 2 months ago by jodes01.
    • This reply was modified 5 years, 2 months ago by jodes01.
    Plugin Support WFAdam

    (@wfadam)

    5 years, 2 months ago

    Thanks for providing that information.

    Looking at the new diagnostic you sent me, it looks like you have it switched to Real IP but it’s pulling in a Cloudflare IP, which is strange because you mentioned cloudflare was disabled when you sent that diagnostic.

    Can you send me a screenshot of your Cloudflare Whitelisted IPs? I would like to verify they are correct. Send me to wftest @ wordfence . com with subject ” jodes01 for WFADAM”. Let me know once you have sent it!

    Thanks again!

    Thread Starter jodes01

    (@jodes01)

    5 years, 2 months ago

    Hi,
    i’ve sent the information !

    Yes cloudflare was on “Suspend Cloudflare on the site”, it was not activated 🙂

    Plugin Support WFAdam

    (@wfadam)

    5 years, 2 months ago

    Thanks for sending that @jodes01

    I have replied with some private information regarding the IP address in the email.

    Also, I see your diagnostic is now reporting a “Too Many Redirects” cURL error instead of the 307 error. I have seen this error usually occur when there is an issue with the SSL. Look in your Cloudflare options for “Always Use HTTPS” and disable this to test. Also, do you have any page rules set in Cloudflare that could be conflicting with Really Simple SSL?

    Let me know what you find!

    Thanks again!

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

The topic ‘Wordfence + Cloudflare : 307 Temporary Redirect’ is closed to new replies.