codesandbox / codesandbox/codesandbox-client
Unable to start devbox VM behind corporate proxy
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
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success: => related, but no solution: https://github.com/codesandbox/codesandbox-client/issues/8074
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
- https://codesandbox.io/dashboard/
- Click on "Create" button
- Choose "JavaScript"
- Choose "Devbox"
- 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
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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