# Problem when connecting to node shell (2025.2.141554)
**URL:** https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731
**Category:** Lens Support & Troubleshooting
**Tags:** new-release, lens-desktop
**Created:** [March 13, 2025, 3:52pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731 "2025-03-13T15:52:04Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@skroehs](https://forums.k8slens.dev/u/skroehs)
#### Post date: [March 13, 2025, 3:52pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/1 "2025-03-13T15:52:04Z")
After upgrading to Lens Version “2025.2.141554-latest” the connect to node shell option seems to be broken.
Trying to connect to a node results in
```auto
E0311 16:01:16.377804 58968 memcache.go:265] couldn't get current server API group list: Get "...": proxyco
nnect tcp: dial tcp: lookup undefined: no such host
Unable to connect to the server: proxyconnect tcp: dial tcp: lookup undefined: no such host
Terminal will auto-close in 15 seconds ...
```
This does not happen in the previous version from january. Connecting to a node shell via kubectl command still works.
---
### Author:  [@jlamoree](https://forums.k8slens.dev/u/jlamoree)
#### Post date: [March 13, 2025, 5:08pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/2 "2025-03-13T17:08:20Z")
Thanks for mentioning this. I thought the problem was me, not Lens.
As a workaround, I got a shell on the node by doing the following:
```auto
kubectl debug node/very-special-hostname -it --image=public.ecr.aws/aws-cli/aws-cli:2.24.22 -- /bin/bash
```
It’s not the same as what Lens creates, but it got the job done.
---
### Author:  [@jonoirwinrsa](https://forums.k8slens.dev/u/jonoirwinrsa)
#### Post date: [March 17, 2025, 7:19am UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/3 "2025-03-17T07:19:21Z")
this is happening for me too
---
### Author:  [@igalatmelingo](https://forums.k8slens.dev/u/igalatmelingo)
#### Post date: [March 19, 2025, 2:15pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/4 "2025-03-19T14:15:03Z")
happening for me as well
---
### Author:  [@skroehs](https://forums.k8slens.dev/u/skroehs)
#### Post date: [March 19, 2025, 3:28pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/5 "2025-03-19T15:28:29Z")
Found another workaround, that solved it for me.
In File-\>Preferences Section “Proxy” you find the option “Lens Internal Proxy” → “Bypass Lens Internal KubeApi Proxy”.
Disabling this option worked for me.
---
### Author:  [@jakolehm](https://forums.k8slens.dev/u/jakolehm)
#### Post date: [March 20, 2025, 11:35am UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/6 "2025-03-20T11:35:31Z")
We would like to understand why the default setting does not work here. Are there anything special with the kubeconfig or the environment that could help us resolve the bug?
---
### Author:  [@skroehs](https://forums.k8slens.dev/u/skroehs)
#### Post date: [March 21, 2025, 2:55pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/7 "2025-03-21T14:55:27Z")
In my scenario i am connecting with aks clusters.
nodes are on version 1.30.6 (OS: linux (amd64), OS Image: Ubuntu 22.04.5 LTS)
I also see in the lens-logs that it creates a temp kubeconfig
```auto
debug: [CLUSTER-KUBECONFIG-MAIN]: Created temp kubeconfig "..." at "...AppData\Local\Temp\kubeconfig-direct-9848c74fb5631a671336ca460e3544d4"
```
The content of this temp kubeconfig looks valid to me. I also tried it out separately by copying this temp-kubeconfig to my .kube-folder and it was usable.
Also when using the node-shell function i see that in namespace “kube-system” it creates a pod “node-shell-(guid)”. This pod is accessible via pod-shell as long as it lives. Which is about 30s. Then the terminal and pod terminate.
---
### Author:  [@noir-lime](https://forums.k8slens.dev/u/noir-lime)
#### Post date: [March 23, 2025, 8:53am UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/8 "2025-03-23T08:53:28Z")
Made an account to just for this issue.
We’re experiencing this on AWS EKS v1.30
Lens version 2025.3.181451-beta
---
### Author:  [@jhbaconshone](https://forums.k8slens.dev/u/jhbaconshone)
#### Post date: [March 23, 2025, 8:53am UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/9 "2025-03-23T08:53:43Z")
I cannot attach a shell to a Pod, is this the same problem? Thanks
---
### Author:  [@jakolehm](https://forums.k8slens.dev/u/jakolehm)
#### Post date: [March 24, 2025, 7:19am UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/10 "2025-03-24T07:19:32Z")
Are there any proxies / vpns required for the connectivity to the cluster?
---
### Author:  [@skroehs](https://forums.k8slens.dev/u/skroehs)
#### Post date: [March 24, 2025, 4:18pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/12 "2025-03-24T16:18:59Z")
@jhbaconshone for me logging to pod-shell worked. If it is a similar problem depends on you log-message which you should shortly see in the terminal or in the logs of Lens.
---
### Author:  [@skroehs](https://forums.k8slens.dev/u/skroehs)
#### Post date: [March 24, 2025, 4:20pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/13 "2025-03-24T16:20:49Z")
No, no specific proxies/vpn. IP-range is restricted, but since the temp-kubeconfig is created on my local system, i would not have expected this to be a factor.
As mentioned in the original post the problem did not occur in version “2025.1.161916-latest”, if this helps.
---
### Author:  [@jhbaconshone](https://forums.k8slens.dev/u/jhbaconshone)
#### Post date: [March 24, 2025, 5:21pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/14 "2025-03-24T17:21:42Z")
Sorry, but I do not understand how you can log to pod-shell? The Shell connection to a pod does not show up in my logs
---
### Author:  [@skroehs](https://forums.k8slens.dev/u/skroehs)
#### Post date: [March 25, 2025, 8:29am UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/15 "2025-03-25T08:29:31Z")
@jhbaconshone You can check this post to find the application logs for lens [https://forums.k8slens.dev/t/where-can-i-find-application-logs/98](https://forums.k8slens.dev/t/where-can-i-find-application-logs/98)
There you find a file “lens.log”
In my case where pod-shell works i just get an info line stating “info: [LOCAL-SHELL]: PTY for … is started with PID=61292”
Maybe you see diffent messages for your case.
---
### Author:  [@jhbaconshone](https://forums.k8slens.dev/u/jhbaconshone)
#### Post date: [March 25, 2025, 5:01pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/16 "2025-03-25T17:01:45Z")
I can see a line like that, but about 150ms later I get that shell has exited for … closed with exitcode=0
What I see is a quick flicker of the shell that disappears.
---
### Author:  [@jhbaconshone](https://forums.k8slens.dev/u/jhbaconshone)
#### Post date: [March 25, 2025, 6:03pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/17 "2025-03-25T18:03:05Z")
I solved my problem on my Mac by removing the kubectl symlink to a non-existent version and the kubectl install inside the Lens Application Support folder - Lens downloaded again and Lens now lets me attach shell to pods again!
---
### Author:  [@piotr.jastrzabek](https://forums.k8slens.dev/u/piotr.jastrzabek)
#### Post date: [April 10, 2025, 8:52am UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/18 "2025-04-10T08:52:20Z")
Same problem for us.
It stopped working with recent updates.
Workaround with switching proxy settings in Lens solve the issue, but
it works only one time… when I try to do it for the second time (different node, same cluster) it just hangs…
Then I just restart Lens and it works again, very annoying…
Do we need vpn to connect to cluster - yes.
Do we have special kubeconfig - quite typical
```auto
- name: arn:aws:eks:eu-central-1:123456789012:cluster/some-cluster
user:
exec:
apiVersion: client.authentication.k8s.io/v1beta1
args:
- --region
- eu-central-1
- eks
- get-token
- --cluster-name
- some-cluster
- --output
- json
command: aws
env:
- name: AWS_PROFILE
value: some-profile
interactiveMode: IfAvailable
provideClusterInfo: false
```
this config is acquired via
aws eks update-kubeconfig --region eu-central-1 --name some-cluster
when it hangs all i see in logs is
```auto
debug: ▪ [NODE-SHELL]: waiting for node-shell-44548936-ea12-4b92-b4c7-3ac577f1f4a6 to be running +120ms
info: ▪ [INTERNAL-PROXY]: watch (pod-3) started /api/v1/namespaces/kube-system/pods?watch=1&resourceVersion=12111828 +1ms
[59085:0409/193303.001980:ERROR:electron_api_service_impl.cc(46)] Attempted to get the 'ipcNative' object but it was missing
[59085:0409/193303.002261:ERROR:electron_api_service_impl.cc(46)] Attempted to get the 'ipcNative' object but it was missing
[59085:0409/193305.243064:ERROR:electron_api_service_impl.cc(46)] Attempted to get the 'ipcNative' object but it was missing
```
---
### Author:  [@phorsmalahti](https://forums.k8slens.dev/u/phorsmalahti)
#### Post date: [April 10, 2025, 8:53am UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/19 "2025-04-10T08:53:12Z")
2025.4.92142-latest has the fix for this issue, please try it out.
---
### Author:  [@skroehs](https://forums.k8slens.dev/u/skroehs)
#### Post date: [April 10, 2025, 11:47am UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/20 "2025-04-10T11:47:32Z")
It works for me with the latest version. Thanks.
---
### Author:  [@murdocay](https://forums.k8slens.dev/u/murdocay)
#### Post date: [April 13, 2025, 2:53pm UTC](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731/21 "2025-04-13T14:53:53Z")
lens 2025.4.92142-latest still can’t connect to node shell, receiving:
Error occurred: Pod creation timed outfailed to open a node shell: failed to create node pod
[Next page](https://forums.k8slens.dev/t/problem-when-connecting-to-node-shell-2025-2-141554/5731.md?page=2)