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
Navigate to [ml.azure.com](https://ml.azure.com/) and select a compute instance.
Attempt to open the instance in Visual Studio Code Desktop.
Observe the following error messages:
"Could not fetch remote environment."
"Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)."
Version: 1.2.0
OS: Windows 10 (10.0.19045)
Product: Visual Studio Code Desktop
Product Version: 1.96.2
Language: en
Additional Information:
Viewing output from "Azure ML - Remote", I see the following errors:
"Workspace is a private endpoint connection."
"Failed to forward incoming connection to remote server: Unexpected server response."
I am on a VPN, and my firewall team has confirmed there are no blocks affecting communication with Azure.
**Notes:**
A previous consultant was able to connect, but both I and a co-worker are unable to.
I have full privileges to the workspace.
I can connect to Visual Studio Code Web, but not the desktop version.
I suspect the issue might relate to:
Outbound firewall rules for the workspace.
A version mismatch or configuration issue.
Request:
Any guidance to troubleshoot and resolve this issue would be greatly appreciated. Thank you! Priscilla
The text was updated successfully, but these errors were encountered:
There is a known issue we planning to fix in the next stable version. When user set Enabled from selected IP addresses in workspace and connect through any IP that not contains in allowed IP list will trigger connection failed.
To work around this issue you can choose two types of solutions
Add your current IP in allowed IP list, and connect your computer through that IP in Public network
Change public network access to Disabled and connect from VNET
Could I please get the link to the website that I can view when this issue is fixed in the next version?
Thank you this worked!
The fix is currently available in the public preview. You can switch to the Pre-Release version and ensure your version number is greater than v1.3.2025012100.
Does this occur consistently?
Yes
Repro Steps:
Details:
Environment Information:
Additional Information:
Request:
Any guidance to troubleshoot and resolve this issue would be greatly appreciated. Thank you! Priscilla
The text was updated successfully, but these errors were encountered: