Lens could not get the logs

[sunset535]

error： Failed to load pods for tab: Failed to GET "****/pods?limit=500": Internal Server Error (500)

[koshevka]

Dear @sunset535

Thanks for reporting a bug. We are working on your issue. Stand by for further updates.

Warm regards, Oleksandr from Lens

[sunset535]

I have no idea where to start resolving this issue, and I can't find this error in the logs.

[koshevka]

@sunset535 may I ask you to check if logs work from kubectl?

[sunset535]

@sunset535 may I ask you to check if logs work from kubectl?

yes , its ok use kubectl in terminal

[sunset535]

i get the log

[sunset535]

[clrothmann]

Hi @sunset535, thank you for reporting the issue! I can see a warning icon on your screenshot. Can you please hover over it and post the content of the info text? Other than that I can see you are not on the current stable version of Lens. Can you please update and tell us if the issue is still present?

[sunset535]

my lens has update the lastest version

[koshevka]

@sunset535 may I ask you to try to update Lens to the latest version 2025.6.261308 and let us know the result, please? As I can see, you're using 2025.6.21515

[sunset535]

it's not working

[sunset535]

[roman-parkhunovskyi]

Same in Lens: 2025.8.121212-latest. So annoying to restart 10-20 times per day.

[yss14]

Yes, same here. every time I restart a deployment and a new pod was created I cannot access the logs of the new pod without restarting Lens.

Lens: 2025.8.121212-latest
Electron: 35.4.0
Chrome: 134.0.6998.205
Node: 22.15.0

[fleetwoodstack]

Same issue - i have to restart Lens (on mac) 5 times a day or so as it fails to get logs for every pod I attempt to view logs for. For some reason the restart each time makes it work for a little longer.

[pezzking]

Same issue here.

from the log:

Tried to inject non-registered injectable "f8b029fa-5ede-4bd4-b89f-1b124d030da8:0ff843767bf8d05b4acfb4ea686584cf:/api/pods" 
-> "start-application" -> ... -> "kube-json-api" -> "create-kube-json-api" -> "legacy-fetch" -> "node-fetch-fetch"

1. Initially, Lens works fine and can display pod logs
2. After ~5 hours of running (based on timestamps in my logs from 05:24 to 08:45), the dependency injection system starts failing
3. The failure affects multiple Kubernetes API endpoints, including: ◦ /api/pods/log (pod logs) ◦ /api/v1/events ◦ /apis/apiextensions.k8s.io/v1/customresourcedefinitions ◦ Various other watchers
4. Pattern: The watch connections keep retrying every 5 seconds but consistently fail with the same injection error

This appears to be a memory/lifecycle management issue in Lens Desktop where: • Injectable dependencies (like the API client for fetching pod logs) get improperly disposed or unregistered • The app continues trying to use these dependencies, causing the failures

Hoping for a fix soon.

Thanks

[Preen]

+1

[diljot-mutti]

Any solution? Seems like this issue is outstanding for long time. Macbook M2 Pro

Lens: 2025.10.230725-latest Electron: 38.2.2 Chrome: 140.0.7339.133 Node: 22.19.0