Connectivity

  • Resolved cdevil666

    (@cdevil666)


    5 years, 1 month ago

    wp_remote_post() test back to this server failed! Response was: 403 Forbidden
This additional info may help you diagnose the issue. The response headers we received were:
HTTP/1.1 403 Forbidden
Date: Thu, 01 Apr 2021 12:40:32 GMT
Server: Apache
Content-Length: 318
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p>You don't have permission to access this resource.</p>
<p>Additionally, a 403 Forbidden
error was encountered while trying to use an ErrorDocument to handle the request.</p>
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support wfpeter

    (@wfpeter)

    5 years, 1 month ago

    Hi @cdevil666, thanks for posting the above error.

    We may be able to get more information about the wp_remote_post() back to your site failing by taking a look at your diagnostics report. Can you send one 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.

    Note: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.

    Thanks,

    Peter.

    Thread Starter cdevil666

    (@cdevil666)

    5 years, 1 month ago

    Hello
    I have sent the report from the website..Please do the needful

    Plugin Support wfpeter

    (@wfpeter)

    5 years, 1 month ago

    Hi @cdevil666, thanks for sending that over!

    It looks as though we are receiving a 403 Forbidden when trying to connect back to your site which is causing the issue. This looks like a default server page though rather than a Wordfence blocking page, so could be blocked by a firewall or other rule somewhere on your hosting environment.

    Check that our latest IPs as highlighted on https://www.wordfence.com/help/advanced/#servers-and-ip-range are allowed by your host or server firewall settings. You may have to reach out to their support for this. We changed IPs during a migration a while ago which went largely unnoticed for most, but there’s a chance your host specifically allowed our old ones and need to update them to prevent you having problems.

    It might be worth also checking your server IP, which you can discover from the Wordfence > Tools > Diagnostics page under “IP(s) used by this server“. See whether that IP appears under Wordfence > Live Traffic or Wordfence > Firewall > Blocking. I don’t think it will but you can choose to “Unblock IP” from both of those screens if it does appear.

    Thanks,

    Peter.

    Plugin Support wfpeter

    (@wfpeter)

    5 years, 1 month ago

    Hi @cdevil666,

    I saw that you were still experiencing the 403s when connecting back into your site with the second diagnostic. Were you able to make progress in the mean time with your host, or Wordfence blocking list regarding allowing of our IPs, or your server IP?

    Thanks again,

    Peter.

    Thread Starter cdevil666

    (@cdevil666)

    5 years, 1 month ago

    There was no issues in connectivity now, Need to check once if there is any connectivity issues. Thanks for the quick response

    Plugin Support wfpeter

    (@wfpeter)

    5 years, 1 month ago

    Hi @cdevil666,

    Thanks for checking again, allowing our IPs should clear up the forbidden issue when we attempt to connect back to your site.

    Peter.

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

The topic ‘Connectivity’ is closed to new replies.