Troubleshooting downstream cluster disconnections and kubectl timeouts in Rancher 2.6.4 and 2.6.5

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


Rancher Version 2.6.4 and 2.6.5 with multiple downstream clusters


Clusters will be unavailable or running kubectl commands from the built-in shell from the UI will timeout.


kubectl get nodes
Unable to connect to the server: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
There are no log errors in rancher or downstream agents
Log nginx: upstream_status="-" upstream_response_time="32.000" request_uri="/k8s/clusters/[cluster]/apis?timeout=32s"



To restart the Rancher Pods:

kubectl rollout restart deploy rancher -n cattle-system ; kubectl rollout status deploy rancher -n cattle-system 




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.

  • Document ID:000020745
  • Creation Date: 01-Sep-2022
  • Modified Date:21-Dec-2022
    • SUSE Rancher

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center