Title: HTTP status code: 403 Forbidden
Last modified: October 30, 2024

---

# HTTP status code: 403 Forbidden

 *  Resolved [Olaf Lederer](https://wordpress.org/support/users/finalwebsites/)
 * (@finalwebsites)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/http-status-code-403-forbidden-2/)
 * Hi,
   I have the same issue as here:[https://wordpress.org/support/topic/http-status-code-403-forbidden/](https://wordpress.org/support/topic/http-status-code-403-forbidden/)
   I disabled NFW and Cloudflare and I’m still getting this error. I also doubble
   checked .htaccess and others. Any other advice?

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

 *  Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/)
 * (@nintechnet)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/http-status-code-403-forbidden-2/#post-18106604)
 * Go to the profiler’s main page, click the “Support” tab and search for `[admin-
   ajax]`.
   Do you see `[access] => OK` or an error instead?
 *  Thread Starter [Olaf Lederer](https://wordpress.org/support/users/finalwebsites/)
 * (@finalwebsites)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/http-status-code-403-forbidden-2/#post-18106756)
 * I think the problem was, that enabling Cloudflare’s “Development mode” is not
   the same as disabling the proxy by making the clouds grey 😉
   Thanks, now it’s
   working
 *  Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/)
 * (@nintechnet)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/http-status-code-403-forbidden-2/#post-18106869)
 * You can try to bypass your CDN by directly accessing the site via its IP address
   and adding the `host` field:
   1. In the “Page to profile”, select “Custom post/
   URL” and enter the server real IP address instead of the domain. For instance:`
   https://1.2.3.4/some-page-to-profile/`2. Then click the “Advanced Options” button
   and in the “HTTP headers” section, enter the “Host” field with your domain name.
   For instance: `Host: example.com`
 * If you block IP addresses that don’t originate from the CDN at your server level,
   that won’t work.
 *  Thread Starter [Olaf Lederer](https://wordpress.org/support/users/finalwebsites/)
 * (@finalwebsites)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/http-status-code-403-forbidden-2/#post-18106912)
 * Thanks for providing this workaround. Disabling the CDN for a test is not a problem.
 * If I need to test more it’s always better to test via the staging environment.

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

The topic ‘HTTP status code: 403 Forbidden’ is closed to new replies.

 * ![](https://ps.w.org/code-profiler/assets/icon-256x256.png?rev=3143506)
 * [Code Profiler - WordPress Performance Profiling and Debugging Made Easy](https://wordpress.org/plugins/code-profiler/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/code-profiler/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/code-profiler/)
 * [Active Topics](https://wordpress.org/support/plugin/code-profiler/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/code-profiler/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/code-profiler/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [Olaf Lederer](https://wordpress.org/support/users/finalwebsites/)
 * Last activity: [1 year, 7 months ago](https://wordpress.org/support/topic/http-status-code-403-forbidden-2/#post-18106912)
 * Status: resolved