codesandbox / codesandbox/codesandbox-client

Unable to start devbox VM behind corporate proxy

Open
#8,802 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 bug report

Preflight Checklist

Description of the problem

We are behind a corporate proxy. We cannot start any sandbox VM or devbox.

In our company all HTTP(S) traffic must go through that proxy. The proxy is configured correctly in the browser. We tested on several different browsers: Firefox, Chorme & Edge. Always the same result.

How has this issue affected you? What are you trying to accomplish?

Goal: Just start any codesandbox VM or devBox.

To Reproduce
  1. https://codesandbox.io/dashboard/
  2. Click on "Create" button
  3. Choose "JavaScript"
  4. Choose "Devbox"
  5. Click "Create DevBox"

The browser starts and starts a VM, but then an error popup is shown: "The workbench failed to connect to the server (Error: WebSocket close with status code 1006)". First error message in browser console is:

websocket-factory.ts:57 WebSocket connection to 'wss://jpkfpt-50000.vscode.codesandbox.io/stable-dc96b837cf6bb4af9cd736aa3af08cf8279f7685?reconnectionToken=eb0cd615-3695-4e3a-ae87-602e9e885a60&reconnection=false&skipWebSocketFrames=false&preview_token=eyJhbGciXXXXXXXXXXXXXXX....XXXXX' failed
Link to sandbox: link
Image
Your Environment
Software Name/Version
Сodesandbox newest, from web page
Browser Google Chorm - Version 140.0.7339.208 (Official Build) (64-Bit), and also same issue in Firefox or Edge
Operating System Windows 11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Devbox creation flow and inspect the first browser-console failure at websocket-factory.ts:57, especially the WebSocket connection shown in the report. Done means a Devbox can start and its workbench connects successfully when HTTP(S) traffic is routed through a corporate proxy.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.