Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when connecting from ML Studio compute instance to Visual Studio Code Desktop WebSocket close with status code 1006 #2486

Open
pmarotte83 opened this issue Jan 8, 2025 · 3 comments
Assignees
Labels

Comments

@pmarotte83
Copy link

Does this occur consistently?

Yes

Repro Steps:

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)."

Details:

Action: Resolver.resolve
Error Type: TypeError
Error Message: Cannot read properties of undefined (reading 'statusCode')

Environment Information:

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

@Siglud
Copy link
Member

Siglud commented Jan 13, 2025

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

@pmarotte83
Copy link
Author

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!

@Siglud
Copy link
Member

Siglud commented Jan 21, 2025

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.

Please also make sure this feature is enabled.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants