Unable to see Rancher GUI, getting 500, 502, 503

This document (000020896) is provided subject to the disclaimer at the end of this document.

Environment

A Kubernetes cluster with Rancher installed.

Situation

When attempting to navigate to the Rancher UI, cannot see the UI and instead are receiving a 500, 502,503 error.

Cause

For HTTP, the 5XX errors (500-511) are server-side errors meaning that the service itself is not responding to queries. The most common errors seen when trying to navigate to Rancher and seeing a 5XX error are:

500 Internal Server Error - Generic error that something is wrong with the server
502 Bad Gateway - Upstream server provided an invalid response
503 Service Unavailable - The server cannot handle the request

Generally speaking, these errors are seen due to either a problem with the ingress or the Rancher pods themselves.
A 5XX error can be corrected by trying to redeploy the Rancher pods, but we should first identified the root cause.

To begin troubleshooting these errors, check that the Rancher pods are running.
If they are all running, check that there are no errors in the Rancher logs.
If everything with the Rancher pods seems healthy, check that your ingress controller pods are also running and not posting errors.
To finish, check your LoadBalancer if any for any logs or any connectivity issues with Rancher nodes.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.