Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Everything works fine, but the final connection keeps loading.#16669

Unanswered
ShuaiQA asked this question inGeneral
Discussion options

Is there an existing issue for this?

  • I have searched the existing issues

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

last workspaces logs:=== No onCreateCommand script specified=== No updateContentCommand script specified=== Running postCreateCommand as the"root" user...=== Running init command as user "root": ["/bin/sh" "-c" "#!/usr/bin/env sh\nset -eux\n# Sleep for a good long while before exiting.\n# This is to allow folks to exec into a failed workspace and poke around to\n# troubleshoot.\nwaitonexit() {\n\techo \"=== Agent script exited with non-zero code ($?). Sleeping 24h to preserve logs...\"\n\tsleep 86400\n}\ntrap waitonexit EXIT\nBINARY_DIR=\"${BINARY_DIR:-$(mktemp -d -t coder.XXXXXX)}\"\nBINARY_NAME=coder\nBINARY_URL=http://103.106.191.182:7080/bin/coder-linux-amd64\ncd \"$BINARY_DIR\"\n# Attempt to download the coder agent.\n# This could fail for a number of reasons, many of which are likely transient.\n# So just keep trying!\nwhile :; do\n\t# Try a number of different download tools, as we don not know what we\n\t# will have available.\n\tstatus=\"\"\n\tif command -v curl >/dev/null 2>&1; then\n\t\tcurl -fsSL --compressed \"${BINARY_URL}\" -o \"${BINARY_NAME}\" && break\n\t\tstatus=$?\n\telif command -v wget >/dev/null 2>&1; then\n\t\twget -q \"${BINARY_URL}\" ⚙️ Creating settings file...Installing code-server!######🥳 code-server has been installedin /tmp/code-server👷 Running code-serverin the background...Check logs at /tmp/code-server.log!open terminal /tmp/code-server.log: cat /tmp/code-server.log [2025-02-21T16:50:01.721Z] info  code-server 4.97.2 34b8d2ed69811c3315a465f01492e9448c9254aa[2025-02-21T16:50:01.724Z] info  Using user-data-dir /root/.local/share/code-server[2025-02-21T16:50:01.759Z] info  Using config file /root/.config/code-server/config.yaml[2025-02-21T16:50:01.759Z] info  HTTP server listening on http://127.0.0.1:13337/[2025-02-21T16:50:01.760Z] info    - Authentication is disabled[2025-02-21T16:50:01.760Z] info    - Not serving HTTPS[2025-02-21T16:50:01.760Z] info  Session server listening on /root/.local/share/code-server/code-server-ipc.sock[16:50:10] [16:50:10] Extension host agent started.

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

ImageThe URL that you click on code-server to jump to is still loading.

Image
Click VS Code, the local vscode cannot be connected.

Image

Environment

  • Host OS: Ubuntu 24.04
  • Coder version: images： ghcr.io/coder/coder:latest、ghcr.io/coder/envbuilder:latest、

Additional Context

No response

You must be logged in to vote

Replies: 2 comments 1 reply

Comment options

hello@ShuaiQA, apologies for the delay, were you able to figure this out?

Regardingcode-server being a blank page, there is an upstream issue in VSCode that caused this.
Seecoder/code-server#7212 (comment) for more context, but the TL;DR is that you should edit the template to install the previous4.96.4 version.

Regarding the 404 error, this happens when clicking "VS Code Desktop", correct?
Could you send the version of Coder that you're running please? It's available in this dropdown.
image

You must be logged in to vote
0 replies
Comment options

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 problem

For 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:

$ docker exec -it <devcontainer> bash

(The name of the devcontainer can be obtained withdocker ps).

I then expected the subagent's log with

$ less /tmp/coder-agent.log

and found lots of messages showing problems with DERP.

The solution

I could probably have fixed something with my reverse proxy, but ultimately, the simpler solution was to setCODER_DERP_FORCE_WEBSOCKETS=true in/etc/coder.d/coder.env, restarting coder and then restarting the workspace. After that, I could successfully access the devcontainer from the web UI.

You must be logged in to vote
1 reply
@kenogo
Comment options

@phorcys420 I'm pinging you because you've contributed to this discussion before. Debugging this issue was a real headscratcher for me, most importantly because my Coder instance's healthcheck says that everything is fine and everything worked besides docker-in-docker devcontainers. Maybe a hint atCODER_DERP_FORCE_WEBSOCKETS=true could be included somewhere in the docs?

https://coder.com/docs/user-guides/devcontainers/troubleshooting-dev-containers

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
3 participants
@ShuaiQA@kenogo@phorcys420
Converted from issue

This discussion was converted from issue #16655 on February 24, 2025 10:40.

[8]ページ先頭
©2009-2025 Movatter.jp