Cannot connect cause of proxy authentication

[K4leri]

Describe the bug
I just installed new version of lens and it tries to use proxy conection for no reason.
I have never use proxy and i dont have set up them.

To Reproduce

1. I decide to install new version
2. after installed i cant connect cause of luck conection to proxy

Expected behavior
I dont wanna my lens use proxy conection if i dont have any proxy conections.

Screenshots

Environment (please complete the following information):

• Lens Setup: 2024.9.300059-latest.exe
• OS: Windows 10 22H2 19045.2965

Kubeconfig:

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: DATA+OMITTED
    server: ...
  name: ...
- cluster:
    certificate-authority-data: DATA+OMITTED
    server: ...
  name: ...
contexts:
- context:
    cluster: ...
    user: ...
  name: yc-general
- context:
    cluster: ...
    user: ...
  name: yc-kube-massive
current-context: yc-general
kind: Config
preferences: {}
users:
- name: ...
  user:
    exec:
      apiVersion: ...
      args:
      - k8s
      - create-token
      - --profile=...
      command: C:\Users\...\yandex-cloud\bin\yc.exe
      env: null
      interactiveMode: IfAvailable
      provideClusterInfo: false
- name: ...
  user:
    exec:
      apiVersion: ...
      args:
      - k8s
      - create-token
      - --profile=easycommerse
      command: ...
      env: null
      interactiveMode: IfAvailable
      provideClusterInfo: false

Aditional content:

• k9s works fine at the same setup.
• Close to Stuck on "Connecting... Authentication proxy started" #2189

[clrothmann]

Thank you @K4leri for your report. I addressed your issue to the corresponding team.

[dechegaray]

Hi @K4leri , the aforementioned proxy is internal to Lens and is there for legacy reasons. In the near future, we are planning to offer an option to opt-out of it, but it has been there for a long time (years I would say)... Can you connect to this cluster through plain kubectl and run for example kubectl get --raw /api?

[K4leri]

@dechegaray yes i can. But the same thing as i am describing in this message:

I found exectly whats wrong. I installed exe to all users on my windows OS. Then i start Lens.exe whithout admin rights and in such case it gives this error to me.

When i start my Lens.exe with admin rights => all is working. So for some reason it should work under admin rights.
I dont know if its an error. If not, then the topic should be closed

[dechegaray]

@dechegaray yes i can. But the same thing as i am describing in this message:

I found exectly whats wrong. I installed exe to all users on my windows OS. Then i start Lens.exe whithout admin rights and in such case it gives this error to me.

When i start my Lens.exe with admin rights => all is working. So for some reason it should work under admin rights. I dont know if its an error. If not, then the topic should be closed

Admin rights should not be required, but if users are under strict security rules, it must be checked that they can execute .exe files from C:\Users\<username>\AppData\. We had another case in which the user had to move Lens' folders to a different location because of its strict setup.

May I suggest the following:

• Uninstall Lens.
• Remove anything in C:\Users<username>\AppData\Local\Programs\Lens
• Install again the latest release.

We had few cases (Windows only) in which remaining files in that location where causing some permission related issues