> For the complete documentation index, see [llms.txt](https://docs.uxwizz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uxwizz.com/guides/troubleshooting/wordpress/cloudways-403-forbidden-screen-on-wordpress.md).

# Cloudways 403 Forbidden screen on WordPress

### Problem:

The UXWizz WordPress dashboard or one of its requests returns **403 Forbidden**.

### Cause:

Cloudways can restrict direct access to PHP files under `wp-content`. UXWizz needs its public dashboard files and PHP endpoints to be reachable. A firewall or another security rule can also produce a 403.

### Solution:

1. Open the browser's **Network** panel, reload the dashboard, and note the exact blocked URL.
2. Check the server or firewall log to identify the rule that blocked it.
3. Ask Cloudways support for an exception limited to the required UXWizz endpoint or plugin paths. Keep private configuration files protected and retain PHP execution rules.
4. Reload the dashboard, sign in, and check that tracking requests succeed.

This requires Cloudways or server administration access. A UXWizz setting cannot override a hosting restriction.

### Cloudways panel workaround

If **Direct PHP Files Access** causes the 403, the original panel workaround is still an option:

1. In Cloudways, open **Servers** and choose the server.
2. Click **www** and select your WordPress application.
3. Open **Application Management → Application Settings**.
4. Record the current **Direct PHP Files Access** setting, then set it to **Enable** and confirm the change.
5. Reload UXWizz and repeat the failed request. If the 403 remains, restore the previous setting and investigate the actual blocking rule.

{% hint style="warning" %}
This switch allows direct PHP access across the WordPress application, including files outside UXWizz. Use it only when you accept that wider scope. Keep WordPress and plugins updated and retain file protections. A host-provided exception limited to UXWizz is preferable; restore the original switch setting if you later use that exception.
{% endhint %}

The setting and its Enable/Disable behavior are described in [Cloudways' PHP access guide](https://support.cloudways.com/en/articles/5127209-restrict-direct-access-to-wordpress-php-files).

If the blocked URL is the dashboard directory itself, also check the [NGINX index-file instructions](/guides/troubleshooting/wordpress/nginx-403-forbidden-screen-on-wordpress.md).