Replies: 2 comments 1 reply
-
|
hello @ShuaiQA, apologies for the delay, were you able to figure this out? Regarding Regarding the 404 error, this happens when clicking "VS Code Desktop", correct? |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue with a Coder instance running behind a reverse proxy. I could not access the devcontainer via SSH nor the Terminal icon in the Coder UI, and code-server would just load infinitely displaying a blank page. I did have access to the outer agent, though, and could verify that the devcontainer was in fact built successfully and the subagent was running inside of it. Diagnosing the problemFor debugging, I first opened a terminal to the main container running the main coder agent. From there, I opened a shell to the devcontainer using:
(The name of the devcontainer can be obtained with I then expected the subagent's log with
and found lots of messages showing problems with DERP. The solutionI could probably have fixed something with my reverse proxy, but ultimately, the simpler solution was to set |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Is there an existing issue for this?
Current Behavior
I deployed it using docker. The health check displayed by opening the interface through the web page was normal. I downloaded Docker (Devcontainer) Templates and created Workspaces. When I clicked on vscode, the local vscode could not be connected and when I clicked on the code-server, the web page kept loading.
Relevant Log Output
Expected Behavior
It is expected that clicking on the local vscode of VS Code Desktop can connect to the remote one, and clicking on the URL redirected by code-server can load the content.
Steps to Reproduce
Click VS Code, the local vscode cannot be connected.
Environment
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions