wp_remote_post() test back to this server failed! Response was: cURL error 7:

  • Resolved cilu

    (@cilu)


    1 year, 3 months ago

    Hi there,
    I’m configuring Wordfence but I get this message

    The changes have not yet taken effect. If you are using LiteSpeed or IIS as your web server or CGI/FastCGI interface, you may need to wait a few minutes for the changes to take effect since the configuration files are sometimes cached. You also may need to select a different server configuration in order to complete this step, but wait for a few minutes before trying. You can try refreshing this page.

    In Diagnostics tool > Connectivity > Connecting back to this site via IPv6 I get this error

    wp_remote_post() test back to this server failed! Response was: cURL error 7:

    I alredy sent the report via email

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @cilu, thanks for sending your diagnostic over!

    The IPv6 connectivity error is harmless when your server software assigns an IPv6 address to your site, but your host doesn’t give you an IPv6 address. As your site seems to work with IPv4, the IPv6 error shouldn’t be affecting the site.

    As you’re running on a CGI/FastCGI server, you could use FTP or a file manager to access your .htaccess file in the root directory and make sure this code is input:

    # Wordfence WAF
<Files ".user.ini">
<IfModule mod_authz_core.c>
    Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
    Order deny,allow
    Deny from all
</IfModule>
</Files>
# END Wordfence WAF

    Then also, in the same directory, add/edit your .user.ini file with this code:

    ; Wordfence WAF
auto_prepend_file = '/your/path/to/wordfence-waf.php'
; END Wordfence WAF

    Make sure to change the path above with the one where wordfence-waf.php actually resides. Your initial issue does at first glance seem to resemble a problem we once saw where a host had denied PHP configuration to its customers, therefore requiring Wordfence to permanently run in Basic Protection. However, please try the above first and possibly consult your host’s support as to whether you have the ability to modify your .htaccess and .user.ini files in this way before reporting back to us.

    Thanks,
    Peter.

    Thread Starter cilu

    (@cilu)

    Hi Peter,
    thanks for your response.

    I added as first line the code in .htaccess file, created the file .user.ini and added the code and changed the path to the wordfence-waf.php file.

    I re-run the config but still. I noticed that the code in .htaccess has been removed, I added it again.

    Plugin Support wfpeter

    (@wfpeter)

    That’s interesting @cilu, were you able to obtain any information from your host on whether they auto-reset any changes made to the .htaccess?

    Thanks,
    Peter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘wp_remote_post() test back to this server failed! Response was: cURL error 7:’ is closed to new replies.