Hi, we're experiencing an issue where we can't `ku...
# general
g
Hi, we're experiencing an issue where we can't
kubectl exec
into any pods on RKE2 clusters and I'm seeing a lot of these entries in the rancher log:
Copy code
...
2025/09/02 16:42:13 [ERROR] error syncing 'fleet-default/vrcvip-us-west-agc-managed-system-upgrade-dc9d0e': handler mcc-bundle: no chart version found for system-upgrade-controller-106.0.0, requeuing
...
2025/09/02 16:14:37 [INFO] RDPClient: Checking if dialer is built...
2025/09/02 16:14:37 [INFO] RDPClient: Dialer is not built yet, waiting 5 secs to re-check.
2025/09/02 16:14:42 [INFO] RDPClient: Checking if dialer is built...
2025/09/02 16:14:42 [INFO] RDPClient: Dialer is not built yet, waiting 5 secs to re-check
...
2025/09/02 16:42:30 httputil: ReverseProxy read error during body copy: http2: server sent GOAWAY and closed the connection; LastStreamID=267, ErrCode=NO_ERROR, debug=""
2025/09/02 16:42:30 httputil: ReverseProxy read error during body copy: http2: server sent GOAWAY and closed the connection; LastStreamID=267, ErrCode=NO_ERROR, debug=""
2025/09/02 16:42:30 httputil: ReverseProxy read error during body copy: http2: server sent GOAWAY and closed the connection; LastStreamID=267, ErrCode=NO_ERROR, debug=""
Does this relate to websockets and any idea how to fix this?
b
Are these windows nodes?
g
No, it's Ubuntu running Rancher on a single node docker install (which I know is not recommended and we are planning to migrate to K8s/K3s but haven't had time yet).
b
I meant the downstream clusters.
g
Oh, those are Debian 12 nodes
b
I asked because the RDP is a windows thing.
Seems like something triggered a client and that's what the blocker is.
It's probably not related to your issue then.
I'd check kubectl against the nodes directly. Edit the config so you're not using the rancher instance as a proxy and just see if you can
kubectl get nodes
or something
g
Ok, this is the error we're seeing on the client side:
Copy code
Chads-MacBook-Pro-2:~ chad$ kubectl exec -it deploy/app -- bash
Error from server (InternalError): an error on the server ("<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body>\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.21.0</center>\r\n</body>\r\n</html>") has prevented the request from succeeding (get deployments.apps app)
And rancher is behind NGINX and there are tons of these in the NGINX log:
Copy code
2025/09/02 16:39:38 [error] 207972#0: *30012 connect() failed (146: Connection refused) while connecting to upstream, client: 10.10.50.203, server: <http://rancher.vrcis.com|rancher.vrcis.com>, request: "GET /v3/connect HTTP/1.1", upstream: "<http://192.168.128.23:80/v3/connect>", host: "<http://rancher.vrcis.com|rancher.vrcis.com>"
b
So it sounds like port 80 is closed on your rancher instance.
nginx is returning a 502 because it' can't reach
<http://192.168.128.23/v3/connect>
g
Ok that may have been when I restarted it. I just started it back up and it automatically crashes with this in the logs:
Untitled.txt
b
6444
throws up a red flag for me. That's not the standard k8s port.
This is probably why docker isn't supported? IDK. I'd edit some of your original message and maybe someone else has an idea.
g
Ok, will do. Thanks anyway.