5XX Errors

Whenever Zynk receives an error that begins with 5XX (E.g. 500, 503, 504 etc), this indicates there is an issue with the server that Zynk is connecting to. Below are some common 5XX errors and what they mean.

Note

Because 5XX errors are a problem on the endpoint that Zynk connects to, the issue needs to be reported to the team that handles the web server in question.

500 Internal Server error

One of the most common 5XX errors is the 500 internal server error. This indicates a generic server error has happened at the endpoint Zynk is connecting to. It is generic because it indicates that the server is unable to determine the exact problem.

502 Bad Gateway

The 502 error indicates that the server that was acting as a gateway or proxy has received an invalid response from the upstream server. This is most common when there are VPNs or other restrictive network protocols in place.

503 Service Unavailable

The 503 error code indicates that the server Zynk is trying to connect to is not ready to handle the request. Common causes are that the service is down for maintenance or it has been overloaded. Most commonly the best way to resolve this would be to wait until the service is available.

504 Gateway Timeout

The 504 Gateway Timeout server error response status code indicates that the server, while acting as a gateway or proxy, did not get a response in time from the upstream server in order to complete the request. This is similar to a 502 Bad Gateway, except that in a 504 status, the proxy or gateway did not receive any HTTP response from the origin within a certain time.