What the status code tells you
- 403 Forbidden means the server understood the request but refused access. Check permissions, security rules and index files.
- 404 Not Found means the requested path was not resolved. Check the URL, document root, rewrite rules and application routes.
- 500 Internal Server Error means the application or server failed while handling the request. The error log is the next step.
- 502 or 503 often indicates an upstream application process, deployment or temporary resource problem.
Isolate the problem
- Confirm whether every page fails or only one URL.
- Note the first failure time and the last change made before it.
- Open the website logs in Enhance and find the first relevant error at that time.
- Check storage and resource usage if failures appear under load or during uploads.
- Temporarily disable the specific plugin, rule or deployment introduced by the last change when it is safe to do so.
- Restore a backup only when rolling back the change manually is not reliable.
For WordPress websites
- Use maintenance or recovery access before changing production files.
- Temporarily enable WP_DEBUG_LOG while keeping public error display off.
- Rename only the suspected plugin directory rather than disabling every plugin without evidence.
- Re-save permalinks after confirming the site URL and rewrite configuration are correct.
- Check that the active theme and PHP version remain compatible.
Escalate with the right details
Send Dprime support the URL, status code, timestamp, action that triggers the error, recent changes and the relevant log lines. Remove passwords, API keys and customer data before attaching a log.