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
ARM Tools extension gets stuck on 'Starting ARM Template Language Server' when using it behind a proxy server like zScaler.
It never progress further and does not seem to timeout either.
Issue might be related to updated chromium proxy server support mentioned here: https://code.visualstudio.com/docs/setup/network#_proxy-server-support
As a workaround, starting VS Code with the following command line ensures that ARM extension works as expected:
"Code.exe" --proxy-server="http=xxxx.xx.local:443;https=xxxx.xx.local:443"
Not having any issues with other extensions.
Does this occur consistently? Yes
Repro steps:
open VS code while behind proxy
open ARM Json file
Starting ARM Template Language Server will pop up and never progress further
Version: 0.15.11
OS: windows
OS Release: Windows 10
Product: Visual Studio Code
Product Version: 1.85.1
Language: en
The text was updated successfully, but these errors were encountered:
ericyew
changed the title
Extension does not support updated VS Code Proxy Support
Extension not working behind automated proxy server config
Jan 3, 2024
ARM Tools extension gets stuck on 'Starting ARM Template Language Server' when using it behind a proxy server like zScaler.
It never progress further and does not seem to timeout either.
Issue might be related to updated chromium proxy server support mentioned here:
https://code.visualstudio.com/docs/setup/network#_proxy-server-support
As a workaround, starting VS Code with the following command line ensures that ARM extension works as expected:
"Code.exe" --proxy-server="http=xxxx.xx.local:443;https=xxxx.xx.local:443"
Not having any issues with other extensions.
Does this occur consistently? Yes
Repro steps:
Version: 0.15.11
OS: windows
OS Release: Windows 10
Product: Visual Studio Code
Product Version: 1.85.1
Language: en
The text was updated successfully, but these errors were encountered: