WPIntell

Source evidence

HTTP status code: 403 Forbidden

Code Profiler – WordPress Performance Profiling and Debugging Made Easy · support · 2024-10-30T13:33:00+00:00

Code Profiler – WordPress Performance Profiling and Debugging Made Easy plugin evidence original source source API
mixedsentiment
mediumseverity
0.78relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 35 rows with source links

17.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Olaf Lederer resolved
Hi, I have the same issue as here: 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? 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? 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 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. 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.

Comments

4 shown
nintechnet 2024-10-31T08:06:00+00:00

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?

Olaf Lederer 2024-10-31T09:07:00+00:00

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

nintechnet 2024-10-31T09:58:00+00:00

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.

Olaf Lederer 2024-10-31T10:16:00+00:00

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.