Hello, I’m having trouble in starting Lens on MacOS Tahoe 26.2 (MBPro M4).
When i start the app and get the “Welcome to Lense“ - I select “Already have a Lense ID“ and then after the authentication i keep getting popup in browser: “Open Lens? http://localhost:xxx wants to open this application. “
when i click the Open Lens button i just keep getting the same popup again and again and not able to log into the app.
See logs from debug mode. I tested in browser that i was able to hit Lens ID and http://localhost both so not sure where is the problem
did nslookup app.k8slens.dev as well from bash and works fine too.
Have disabled Ad Blocker in Chrome. Tried deleting extension folder as well. Have already tried reinstalling few times and also deleting the Lense folder under Library/Application support
Appreciate any help…
error: ┏ [TOKEN-REFRESHER]: Unknown error .isAuthenticated() returns false +302ms
error: ┃ [1] Error: .isAuthenticated() returns false
error: ┃ [2] at c.numOfAttempts [as request] (/Applications/Lens.app/Contents/Resources/app.asar/static/build/main.js:1690:51524)
error: ┗ [3] at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
info: 
[LENS-ID-AUTH]: Calling login callback with code +146ms
debug: [LENS-ID-AUTH]: Fetching auth tokens from https://app.k8slens.dev/auth/realms/lensCloud/protocol/openid-connect/token using redirect_uri: http://localhost:51828/login and client_id: lens-extension +0ms
error: ┏ [LENS-ID-AUTH]: Failed retrieve authentication tokens request to https://app.k8slens.dev/auth/realms/lensCloud/protocol/openid-connect/token failed, reason: getaddrinfo ENOTFOUND http +21ms
error: ┃ [1] FetchError: request to https://app.k8slens.dev/auth/realms/lensCloud/protocol/openid-connect/token failed, reason: getaddrinfo ENOTFOUND http
error: ┃ [2] at ClientRequest. (/Applications/Lens.app/Contents/Resources/app.asar/static/build/main.js:203:19041)
error: ┃ [3] at ClientRequest.emit (node:events:531:35)
error: ┃ [4] at emitErrorEvent (node:_http_client:107:11)
error: ┃ [5] at _destroy (node:_http_client:954:9)
error: ┃ [6] at onSocketNT (node:_http_client:974:5)
error: ┃ [7] at process.processTicksAndRejections (node:internal/process/task_queues:91:21)
error: ┗ [8] { type: ‘system’, errno: ‘ENOTFOUND’, code: ‘ENOTFOUND’, erroredSysCall: ‘getaddrinfo’ }
Hello @liftersoutfits0v, Thank you for reaching out! We have received your request and will get back to you as soon as we have some information.
Hi @liftersoutfits0v,
Please try the following workaround:
1. Close all Lens-related browser tabs completely
2. Open your browser and sign in directly at Lens ID
3. Once signed in, restart Lens Desktop and click “I already have a Lens ID”
The getaddrinfo ENOTFOUND http error in your logs suggests the app may be malforming the authentication URL. We’re aware of this pattern and are working on a redesigned activation flow that will address the browser-to-app handoff more reliably.
If the workaround above doesn’t resolve it, please let us know and we can try additional troubleshooting steps.
thanks - I had tried that already and that’s when i was getting the repeated prompts to start Lense. When i attempted that without being logged in - i was prompted to login via Github and then again same pattern resumed.
Do you have proxies disabled? There was a user who had configured “NO PROXY" that caused the same error in the past.
I just tried disabling all proxies in bash env/network seetting/browser and got the same error.
Interestingly I was able to run lense in another macbook though. That was my personal one and did not have the corporate proxies etc - is there a way i could move config files as i will be using same account on both?
Hi @liftersoutfits0v, thanks for testing that – it’s very helpful to know it works on your personal Mac but not on the corporate one. This strongly suggests that something in the corporate network environment is interfering, even with proxies disabled (it could be a firewall, SSL inspection, or certificate trust issue).
A few things to try:
- Check if your corporate Mac has any MDM-managed certificates or SSL inspection (e.g., Zscaler, Netskope) – these can block Lens’s auth flow
- Try connecting to a non-corporate network (e.g., mobile hotspot) on the affected Mac to isolate the issue
- Regarding config migration – your Lens ID syncs automatically when you sign in, so your clusters and settings should appear on any Mac once logged in. No manual config file copying needed.
well, i tried that anyway and it worked!!
just copied ~/Library/Application Support/Lens directory from my personal mac to corp mac and started Lens on corp mac
It gave me has some hash mismatch error and that Lense will be reset - when i accepted it to do what it wanted to - it just came up as a fresh install fully working and my id logged in. Hope it helps someone 
Hi @liftersoutfits0v, that’s great news – thanks for following up! Appreciate you sharing the workaround for others who might run into the same issue.