When a webpage is requested through a browser, the server sends an HTTP status code in response. The status code indicates success, failure, a redirect, or a server problem. While they often appear as simple numbers like 404 or 500, HTTP status codes provide important insight into how websites, applications, and servers are functioning.
VPS owners can use status codes as diagnostic tools to indicate problems such as permissions, files, redirects, applications, and server performance. Moreover, status codes can also indicate if an issue is client-side or server-side.
This guide will break down the classes of HTTP status codes, analyze what the most common of these responses mean, and let VPS users know how they can troubleshoot each.
Key Takeaways
- HTTP status codes fall into five classes: informational, success, redirection, client errors and server errors.
- These codes are useful for diagnosing issues with servers on a VPS.
- A 4xx response identifies a client-error class, but configuration on the server may still be responsible.
- The most common errors are 404, 403, 500, 502, 503, and 504.
- A status code is a starting point for diagnosis; confirm the cause in logs.
- Codes for redirects, 301 and 302, are also important to site migrations and to SEO.
- VPS owners can use status codes to maintain server performance and server reliability.
What Are HTTP Status Codes?
When a user sends a request to the server via a browser or application, the server gives a numeric response to the request, called the HTTP Status Code. Moreover, each code indicates the status of the request in the server standard.
An HTTP response includes a status code along with headers and, where appropriate, a body. The code tells the client how the server handled the request; it is not a complete diagnosis by itself.
HTTP Status Codes are classified into five categories. Moreover, each category simplifies and enhances the understanding of the responses. The five categories and their meanings are as follows:
- 1xx: Informational responses
- 2xx: Successful responses
- 3xx: Redirection messages
- 4xx: Client errors
- 5xx: Server errors
Why HTTP Status Codes Matter for VPS Owners
Status codes help narrow an investigation. Compare the requested URL, response time and logs to determine which service generated the response.
The 4xx class describes client-error responses and the 5xx class server-error responses. A server-side configuration mistake can still cause a 4xx response, so the class alone does not establish who caused the problem.
In VPS settings, status codes help monitor the health of applications and infrastructure. Furthermore, they identify configuration and service issues and help track deployment status to see if deployments might break and become bigger problems.
Understanding HTTP Status Code Categories
HTTP defines five response classes. The first digit identifies the class, while the complete three-digit code gives a more specific meaning.
1xx Informational
1xx codes represent informational responses. Requests are received, and these codes signify that the server is processing the requests. Moreover, such codes are rarely visible while browsing the Internet. They are mainly used for advanced HTTP communication between clients and servers.
Examples:
- 100 Continue: The server has received the request headers, and the client can send the request body.
- 101 Switching Protocols: The server is changing to a different protocol at the client’s request.
2xx Success
2xx codes mean that a request has been received, understood, and accepted. These codes are the expected and most common responses while browsing websites.
Examples:
- 200 OK: The request was successful, and the server returned the requested resource.
- 201 Created: A resource was successfully created on the server.
- 204 No Content: The request was successful, but there is no content to return.
3xx Redirection
The 3xx class covers redirection responses and cache validation. A 304 response is not a redirect to another URL; it tells a conditional requester to reuse a stored representation.
Examples:
- 301 Moved Permanently: The resource has a permanent new address.
- 302 Found: A response code that tells that the resource is temporarily located at a new address.
- 304 Not Modified: The requested resource has not changed since the last visit, so the browser can use its cached version instead of downloading it again.
- 307 Temporary Redirect: The resource is temporarily redirected while preserving the request method.
- 308 Permanent Redirect: The resource is permanently redirected while preserving the request method.
4xx Client Errors
This status code shows that there is a problem with the request the client has made. Moreover, this is most likely due to a missing page, a request to a resource that you cannot access, or an invalid request.
Examples:
- 400 Bad Request: The 400 Bad Request means the server could not understand the request due to malformed syntax.
- 401 Unauthorized: A request that requires authentication has failed.
- 403 Forbidden: The server understood the request but refuses to fulfill it.
- 404 Not Found: The requested resource is not available at the server.
- 405 Method Not Allowed: A request was made using a method that is not allowed.
- 408 Request Timeout: The server waited too long for the request to complete.
- 409 Conflict: The 409 conflict means the requested operation cannot be completed due to a conflict with the state of the target resource.
- 410 Gone: Access to the resource is no longer available and is likely to remain unavailable.
- 429 Too Many Requests: The user has sent too many requests in a given amount of time.
5xx Server Errors
A 5xx response means a server encountered a failure or could not perform the requested operation. The response may come from the origin, an application, a proxy or a CDN.
Some examples:
- 500 Internal Server Error: An unexpected server condition prevented the request from completing.
- 501 Not Implemented: The server cannot process the request because it does not implement the requested functionality.
- 502 Bad Gateway: A gateway or proxy received an invalid response from an upstream server.
- 503 Service Unavailable: The server is unable to handle the request.
- 504 Gateway Timeout: A gateway or proxy did not receive a timely upstream response.
Most Common HTTP Errors VPS Owners Encounter
The same error code can have several causes. Use the following examples to choose what to inspect, then confirm the cause in the relevant logs.
- 403 Forbidden: Check access rules, file ownership, directory permissions and any WAF decision. Access may also be intentionally restricted.
- 404 Not Found: means the resource is not on the server. Missing resources (404’s) on the server are because of misconfigured URLs, server files are deleted or missing, or a misconfigured and faulty server routing.
- 500 Internal Server Error: Internal Server Error is one of the most common server-side errors. Therefore, the server could be misconfigured, crashed, or the scripts on the server could be misconfigured.
- 502 Bad Gateway: Inspect the configured upstream, PHP-FPM or application service and its logs for connection or response errors.
- 503 Service Unavailable: The server is busy and cannot complete your request. This error is due to the down server for maintenance, the service is overloaded, or resources (e.g., CPU) are being exhausted.
- 504 Gateway Timeout: The server did not receive a timely response from the proxied service. Therefore, it happens when the applications, database, or proxy are slow, or if there is some other kind of delay.
How to Troubleshoot HTTP Errors on a VPS
Record the failing URL, request method, exact time and time zone, response code and any request ID. Reproduce the issue once, then correlate the request with logs before changing configuration.
Examine logs: On a typical Ubuntu installation, check the paths below. Custom virtual hosts, containers and managed environments may use different locations.
/var/log/nginx/access.log/var/log/nginx/error.logFor Apache servers, check:
/var/log/apache2/access.log/var/log/apache2/error.logInspect the server configuration: Check virtual hosts, rewrites and upstream addresses. Validate with sudo nginx -t or sudo apache2ctl configtest before reloading the relevant server.
Check file permissions: Compare ownership, directory traversal permissions and access rules with the web-server user. Do not use chmod 777 as a general repair.
Check services: Inspect the service used by your setup. These examples are for Ubuntu; replace php8.3-fpm with the installed PHP-FPM unit. Press Q to exit the status pager.
systemctl status nginx
# Or, for Apache:
systemctl status apache2
# If your application uses PHP-FPM:
systemctl status php8.3-fpmA failed upstream service can produce gateway errors. Check why it failed before restarting it, and preserve useful logs.
Check proxies and CDNs: Compare response headers and request IDs to identify the responding layer. A private browser window does not bypass a shared CDN cache. Use the authorized origin/CDN diagnostic procedure rather than assuming every cached error is a browser problem.
HTTP Status Codes and SEO
Search engines use status codes when crawling and indexing. The response should match the content: a missing page should not return 200 with an error message, and an available page should not return an error status.
301 and 302 redirects: A 301 is a permanent move; a 302 is temporary. Google uses permanent redirects as a stronger canonicalization signal and temporary redirects as a weaker one. It is inaccurate to say that a 302 never passes ranking signals. Use the response that reflects the actual move.
404 and 410 responses: Both tell Google that content is unavailable and can result in removal from the index. Use a relevant redirect when content has genuinely moved; do not redirect unrelated missing pages to a generic destination solely to hide 404s.
5xx errors and crawling: Persistent server failures can slow Google’s crawling, and URLs may eventually leave the index. For temporary maintenance, return the appropriate 503 response and, where useful, a Retry-After header. See Google’s status-code guidance.
“the server encountered an unexpected condition that prevented it from fulfilling the request.”
HTTP Status Code Reference Table
| Status Code | Meaning | Category | Common Cause |
|---|---|---|---|
| 200 | OK | Success | Request completed successfully |
| 301 | Moved Permanently | Redirect | Page permanently moved to a new URL |
| 302 | Found | Redirect | Temporary redirect to another URL |
| 400 | Bad Request | Client Error | Invalid or malformed request |
| 401 | Unauthorized | Client Error | Missing or invalid authentication |
| 403 | Forbidden | Client Error | Permission or access restrictions |
| 404 | Not Found | Client Error | Missing page or incorrect URL |
| 408 | Request Timeout | Client Error | The client took too long to send the request |
| 429 | Too Many Requests | Client Error | Rate limiting or traffic spike |
| 500 | Internal Server Error | Server Error | Application or configuration failure |
| 502 | Bad Gateway | Server Error | Invalid response from upstream server |
| 503 | Service Unavailable | Server Error | Server overload or maintenance |
| 504 | Gateway Timeout | Server Error | Upstream server response delay |
Why UltaHost Works for Server Management and Troubleshooting
Root or sudo access can help you inspect web-server configuration, service state and logs. On managed plans, confirm which tasks your provider handles and which remain your responsibility.
Access to diagnostics: Correlate web-server and application logs with the failing request.
Control over the environment: Adjust the relevant service only after identifying the fault and making a backup of its configuration.
Visibility of logs and configuration: Check what access and support are included in the specific plan before relying on them.
Conclusion
An HTTP status code tells you how a request was handled. Start with the code, URL, time and logs, then identify whether the response came from the application, web server or an upstream service.
After a fix, repeat the original request and confirm both the status code and the expected content. Monitor for recurrence rather than treating a single successful reload as proof that the cause is resolved.
FAQ
What is an HTTP status code?
It is a server response that shows whether a request was successful, failed, or redirected.
What does a 404 error mean?
It means the requested page or resource cannot be found on the server.
What causes a 500 internal server error?
Server misconfigurations, broken scripts, or application crashes usually cause it.
What is the difference between 301 and 302 redirects?
A 301 is permanent, while a 302 is temporary.
Why are HTTP status codes important for VPS owners?
They help identify server issues quickly and improve troubleshooting and monitoring.
