An HTTP status code describes how a server handled a request. Not every status is an error: 2xx codes indicate success, 3xx codes describe redirects, and 4xx or 5xx codes indicate problems that may require investigation.
Common problems
- 400 — Bad Request: the server could not process the request. Check the URL; if the problem is limited to one browser, test a private window.
- 401 — Unauthorized: the resource requires valid authentication. Use the correct sign-in method and account.
- 403 — Forbidden: access was refused. Possible causes include access rules, permissions, or a security block. Do not make files or folders writable by everyone as a quick fix.
- 404 — Not Found: the requested resource was not found. Check the link, page availability, redirects, and application routing.
- 429 — Too Many Requests: a rate limit was reached. Wait before retrying; repeated automated retries can prolong the problem.
- 500 — Internal Server Error: the server or application failed unexpectedly. Note recent changes and ask support to review the relevant logs.
- 502 — Bad Gateway / 504 — Gateway Timeout: a gateway had a problem communicating with an upstream service.
- 503 — Service Unavailable: the service is temporarily unavailable, for example during maintenance or overload.
Help us diagnose it
Send the exact URL, code or message, time and time zone, and whether other pages or devices are affected. Mention recent plugin, application, DNS, or configuration changes. A screenshot can help, but exclude private account information.
If a form or checkout failed, check whether it completed before submitting again. Clearing a browser cache is not a general repair for server errors.
Need help? Open a support ticket. Include the affected domain and the exact error message, but do not include your password.
