Title: Diagnostics Error (connect back) Last modified: July 28, 2021 --- # Diagnostics Error (connect back) * Resolved [barrychapman](https://wordpress.org/support/users/barrychapman/) * (@barrychapman) * [4 years, 10 months ago](https://wordpress.org/support/topic/diagnostics-error-connect-back/) * In the WordFence Diagnostics, I see the following error * 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 Server: CloudFront Date: Wed, 28 Jul 2021 16:39:00 GMT Content-Type: text/html Content-Length: 919 Connection: close X-Cache: Error from cloudfront Via: 1.1 e9a02c3aa85d921b20debfa4cdea5e4.cloudfront.net (CloudFront) ``` * And the HTML: * ``` ERROR: The request could not be satisfied

403 ERROR

The request could not be satisfied.

Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

       Generated by cloudfront (CloudFront)
       ```
   
 * What is causing this error? Everything looks correct, and I can access the site
   fine

Viewing 1 replies (of 1 total)

 *  Plugin Support [WFAdam](https://wordpress.org/support/users/wfadam/)
 * (@wfadam)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/diagnostics-error-connect-back/#post-14712946)
 * Hello [@barrychapman](https://wordpress.org/support/users/barrychapman/) and 
   thanks for reaching out to us!
 * It looks like what is happening is Cloudfront is blocking Wordfence requests 
   to the Wordfence server and back to your site. This is why you see Cloudfront
   in the HTML, as it’s delivering a 403 block to the Wordfence server.
 * We might need to do this in two parts:
 * 1) We want to make sure your site has all the correct settings to run with Cloudfront:
   
   Navigate to Wordfence > All Options > General Wordfence Options > How does Wordfence
   get IPs and change this setting to Use the X-Forwarded-For HTTP header. After
   that, you will need to add the Cloudfront server IPs to the trusted proxies. 
   You will see Edit Trusted Proxies at the bottom of this same section in All Options.
 * Add all of the Cloudfront IP’s from this link into the Trusted Proxies: [http://d7uri8nf7uskq.cloudfront.net/tools/list-cloudfront-ips](http://d7uri8nf7uskq.cloudfront.net/tools/list-cloudfront-ips)
 * 2) Make sure your site and Cloudfront are not blocking the following IPs:
    44.239.130.172
   44.238.191.15 35.155.126.231
 * Once you get this in place, it should resolve the issues you are seeing. Let
   me know how it goes!
 * Thanks again!

Viewing 1 replies (of 1 total)

The topic ‘Diagnostics Error (connect back)’ 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

 * [CloudFront](https://wordpress.org/support/topic-tag/cloudfront/)

 * 1 reply
 * 2 participants
 * Last reply from: [WFAdam](https://wordpress.org/support/users/wfadam/)
 * Last activity: [4 years, 10 months ago](https://wordpress.org/support/topic/diagnostics-error-connect-back/#post-14712946)
 * Status: resolved