HTTP Error 500: Internal Server Error

[bernardoforcillo]

Actual Behavior

HTTP Error 500: Internal Server Error Get "https://172.31.44.231:6443/api/v1/namespaces?includeObject=Object&limit=100000": dial tcp 172.31.44.231:6443: connectex: Impossibile stabilire la connessione. Risposta non corretta della parte connessa dopo l'intervallo di tempo oppure mancata risposta dall'host collegato.

Steps to Reproduce

open dashboard after changing kubectl context.

Result

Expected Behavior

rancher dashboard (i can't access throught kubectl)

Additional Information

No response

Rancher Desktop Version

1.6.0

Rancher Desktop K8s Version

1.24.6

Which container engine are you using?

containerd (nerdctl)

What operating system are you using?

Windows

Operating System / Build Version

Windows 11 Pro Ver. 22000.1098

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

deb

Windows User Only

NordVpn

[bernardoforcillo]

The only solution i found is factory reset.

[gunamata]

I couldn't repro the issue. Here are the steps I followed.

• Create a 2 node cluster following the steps in this doc
• Switch between the default Rancher Desktop context (rancher-desktop) and the one I created. And Open Dashboard from the system tray menu.

@bernardoforcillo - Do you mind sharing the steps you followed to get to this error please?

[bernardoforcillo]

Hi @gunamata I setup a production k3s cluster to kubeconfig. Btw, I think is a systematic error of windows container engine on Windows 11. In the last few weeks I had a lot of error.

[gunamata]

@bernardoforcillo , I hope it's not a remote production k3s cluster that you are trying to use with Rancher Desktop. If yes, As noted in this other issue by you as well, Rancher Desktop doesn't support that use case.

Are you able to consistently reproduce the issue with a local kubernetes cluster? If yes, Do you mind sharing the log files please? You can navigate to the log files folder by clicking on the Show Logs button under the Troubleshooting menu.

[bernardoforcillo]

The other issue is a feature request. At the moment i really don't know how to reproduce the issue with a local kubernetes cluster. in case the same error will append, i will share the logs here.

[bernardoforcillo]

I retried ...

[gunamata]

@bernardoforcillo , I couldn't respond after my last message as I couldn't repro the issue and didn't have anything to share. However, Today I ran into the exact same error pop up as yours when I accidentally tried launching a Rancher Desktop session, while the app is already running on my machine. It could be the same reason you ran into the error. Were you trying to launch a session while there's already a session running or in the process of starting? When you run into this error next time, Can you please make sure there are no active or dangling Rancher Desktop sessions on your machine, and give it a retry?

Also, we do have a issue, https://github.com/rancher-sandbox/rancher-desktop/issues/2437 on our backlog to correctly handle the scenario of launching the app while a session is already active or in the process of launching.

[bernardoforcillo]

The last is the #2437.