You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Because I have very little privileges on my managed windows machine, I use a Linux VM in the cloud where I have full admin access and I run Visual Studio Code with the "Remote-SSH" extension (https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh). The GUI Client runs on my managed windows desktop machine, the server runs on the Cloud Linux VM.
Now when I open a Kotlin project, it tries to download some stuff from Github and I get the following error message:
Could not update/download Kotlin Debug Adapter: Error: Could not fetch from GitHub releases
API: RequestError: Error: getaddrinfo ENOTFOUND my-companys-proxy.net:80.
My educated guess is that it tries to download the Kotlin adapter on the Linux server, but it uses the proxy settings from the windows machine, which is an internal DNS name not visible to the cloud instance.
Expected behavior
Any code that runs on the server side should use the proxy settings from the linux server environment (actually, no proxy in my case).
Extension version
0.2.10
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Because I have very little privileges on my managed windows machine, I use a Linux VM in the cloud where I have full admin access and I run Visual Studio Code with the "Remote-SSH" extension (https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh). The GUI Client runs on my managed windows desktop machine, the server runs on the Cloud Linux VM.
Now when I open a Kotlin project, it tries to download some stuff from Github and I get the following error message:
My educated guess is that it tries to download the Kotlin adapter on the Linux server, but it uses the proxy settings from the windows machine, which is an internal DNS name not visible to the cloud instance.
To Reproduce
Expected behavior
Any code that runs on the server side should use the proxy settings from the linux server environment (actually, no proxy in my case).
Extension version
0.2.10
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: