Common HTTP Error Codes
404 Not Found
-
Description: This error code indicates that the server cannot find the requested resource. It typically occurs when the URL is incorrect or the page has been moved or deleted.
-
Screenshot Guidance: Capture the error page as it appears on different browsers, highlighting the URL bar and the error message.
-
Troubleshooting Steps:
-
Verify the URL for accuracy.
-
Refresh the page or try accessing it at a later time.
-
Clear browser cache and cookies.
-
-
Include in Connectwise Ticket:
-
Confirm the exact URL accessed.
-
Note whether this issue occurs with multiple users or devices.
-
Indicate if the page has recently been moved or removed.
500 Internal Server Error
-
Description: This error code signals a generic server-side problem. It often indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
-
Screenshot Guidance: Capture the full error message and any additional details provided.
-
Troubleshooting Steps:
-
Refresh the page after a few minutes.
-
Try accessing the site from a different browser or device.
-
Clear the browser's cache and cookies.
-
-
Include in Connectwise Ticket:
-
Note the time and frequency of the error.
-
Include details of the specific page or action that triggered the error.
-
Provide any server logs or additional error details if available.
502 Bad Gateway
-
Description: This error indicates that the server received an invalid response from an upstream server. It’s often related to server communication issues.
-
Screenshot Guidance: Highlight the error message and any relevant information about the upstream server.
-
Troubleshooting Steps:
-
Refresh the page or try again later.
-
Check if other sites are accessible.
-
Clear the browser cache and cookies.
-
Restart the browser or try a different one.
-
-
Include in Connectwise Ticket:
-
Document the URL and time when the error occurred.
-
Mention if the issue is affecting multiple users.
-
Provide any relevant logs or network traces.
503 Service Unavailable
-
Description: This error occurs when the server is temporarily unable to handle the request, often due to server overload or maintenance.
-
Screenshot Guidance: Capture the error page, including any message about server overload or maintenance.
-
Troubleshooting Steps:
-
Wait a few minutes and refresh the page.
-
Make sure there has nor been any announced maintenance or downtime.
-
-
Include in Connectwise Ticket:
-
Note the exact time and any pattern of occurrence.
-
Indicate if the issue persists or is intermittent.
-
Include details of any ongoing server maintenance.
504 Gateway Timeout
-
Description: This error indicates that the server did not receive a timely response from an upstream server. It’s usually caused by heavy server load or a network issue.
-
Screenshot Guidance: Highlight the error message and the URL.
-
Troubleshooting Steps:
-
Refresh the page or try accessing the site later.
-
Test the connection on a different network or device.
-
Clear the browser cache and cookies.
-
-
Include in Connectwise Ticket:
-
Provide details on the URL and time of the error.
-
Document any other affected services or sites.
-
Include network diagnostics if available.
403 Forbidden
-
Description: This error occurs when the server understands the request but refuses to authorize it. It could be due to permission issues or IP blocking.
-
Screenshot Guidance: Capture the full error message and any relevant details about access restrictions.
-
Troubleshooting Steps:
-
Check if the URL is correct and accessible.
-
Clear browser cookies and try again.
-
Make sure you are connected to the ALTA network. If remote, make sure you are connected through Sophos.
-
-
Include in Connectwise Ticket:
-
Confirm the URL and user credentials.
-
Note if the issue is isolated to specific users or locations.
-
Include details about any recent changes to access permissions.
401 Unauthorized
-
Description: This error occurs when authentication is required, but the credentials provided are invalid. It’s commonly seen when trying to access restricted areas without proper login.
-
Screenshot Guidance: Highlight the error message and any login prompts.
-
Troubleshooting Steps:
-
Ensure that the correct login credentials are used.
-
Clear the browser cache and cookies.
-
Try accessing the site with a different browser or device.
-
-
Include in Connectwise Ticket:
-
Document the URL and user credentials used.
-
Note if other users are experiencing similar issues.
-
Include any relevant access logs or authentication details.
400 Bad Request
-
Description: This error indicates that the server cannot process the request due to client-side issues, such as malformed syntax or invalid parameters.
-
Screenshot Guidance: Capture the error message and any details about the malformed request.
-
Troubleshooting Steps:
-
Double-check the URL and any query parameters for errors.
-
Clear the browser cache and cookies.
-
Try a different browser or device.
-
-
Include in Connectwise Ticket:
-
Note the URL and specific request details.
-
Indicate whether the error occurs consistently or intermittently.
-
Include any relevant request logs or client-side details.
