> 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/nginx-403-forbidden-screen-on-wordpress.md).

# NGINX 403 Forbidden screen on WordPress

### Problem:

The UXWizz WordPress dashboard returns **403 Forbidden** or **404 Not Found**.

### Cause:

The server may not load `index.html` for the plugin's dashboard directory. The files may also be missing, or a hosting/firewall rule may block the request.

### Solution:

1. Check that the plugin dashboard's `index.html` exists. For the usual plugin path, try opening `/wp-content/plugins/wp-usertrack/userTrack/index.html` on your HTTPS site.
2. If that file loads but the directory URL does not, ask your administrator to set the directory index to `index.html` for this path.
3. Add or adjust the following location inside the site's **existing HTTPS server configuration**. Use your actual plugin path, and merge it with any existing matching location:

   ```nginx
   location /wp-content/plugins/wp-usertrack/userTrack/ {
       index index.html;
   }
   ```
4. Preserve the site's PHP handling, file protections, and other location rules. Test the complete configuration with `nginx -t` before the administrator reloads NGINX.
5. Open the directory URL with its trailing slash. Check sign-in, dashboard requests, and tracking.

This example changes directory-index selection. It is not a complete NGINX configuration or a replacement for access controls. See the [NGINX index module](https://nginx.org/en/docs/http/ngx_http_index_module.html).

### Still not working?

Inspect the exact failed URL in the browser's **Network** panel and the matching server or firewall log entry. A 403 on a PHP endpoint needs a different fix from a missing directory index.

Ask the host for an exception limited to the required public UXWizz paths. Keep private configuration files inaccessible, and do not allow an entire `wp-content` directory or disable a firewall globally. For Cloudways, see [its PHP access restriction](/guides/troubleshooting/wordpress/cloudways-403-forbidden-screen-on-wordpress.md).