Closed general

Setup stopped at Sign in to Adom, then activate the editor

fernando magallanes jr. · 15d ago ·closed by John Lauer

Filed from Hydrogen Desktop 1.0.666 on LAPTOP-07PVL3D8 (setup card).

Hi, im unable to sign in to Adom. VS code is stuck on loading screen pane and even though ive asked claude to help me diagnosing this issue, it didnt work. its pointing me to the WSL of my computer and tried fixing it by changing the $env:USERPROFILE.wslconfig; didnt fix it. Is it really a problem of my computer that im unable to continue? Thanks

Device: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515JAB_X515JA (AMD64, 23.7 GB RAM, Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz). Microsoft Windows 11 Home Single Language 24H2 build 26100. WSL: WSL version: 3.0.3.0.

Attachments: hydrogen-desktop-tail.log (last 300 KB of the app log), diagnostics.json (health, setup state, WSL status, the Doctor checks, build info, device), setup-steps-wsl.json (setup step log), setup-timing-wsl.json (setup step log).

Last 40 log lines:

10:37:42.734 [heartbeat] alive 470s
10:37:52.346 [telemetry] heartbeat activate-editor : HTTP 200
10:37:52.737 [heartbeat] alive 480s
10:38:02.739 [heartbeat] alive 490s
10:38:12.743 [heartbeat] alive 500s
10:38:15.632 [run_all_wsl] DONE 'activate-editor' in 455.3s (failed)
10:38:15.722 [run_all_wsl] HALT: step 'activate-editor' failed after 3 attempts; not advancing to later steps
10:38:15.737 [run_all_wsl] persisted setup-state.txt = in-progress (GET /setup/state matches the cascade)
10:38:15.738 [run_all_wsl] TIMING total 455.5s over 1 steps; slowest: activate-editor 455.3s
10:38:15.747 [cascade] setup released the editor (opportunistic healers re-armed)
10:38:15.765 [run_all_wsl] install-approval window closed, normal prompting restored
10:38:15.766 [taskbar] cascade ended with a failure, leaving the red progress bar up
10:38:15.767 [wsl-startup] auto-run run_all_wsl finished: Ok("{\"completed\":5,\"failed\":1,\"failures\":[{\"error\":\"  ✓ workspace env bound to this launch (proxy :47083, 4 vars)\\n  ✓ api key written through (tools authenticate)\\n  ✓ relay ensured (:8765/:8766)\\nReloading editor iframe + verifying the :8821 editor-control API is live (adom-vscode is baked; this proves it activated)...\\n  … one re-bind of the editor iframe (still waiting ~40s for the extension to activate; NOT reloading repeatedly, each reload restarts the extension host)\\n  ✗ :8821 never answered after ~90s, the adom-vscode extension did not load. HALTING.\",\"step\":\"activate-editor\"}],\"ok\":false,\"timings\":[{\"id\":\"activate-editor\",\"ms\":455329,\"ok\":false}],\"total\":8,\"total_ms\":455454}")
10:38:15.768 [wsl-startup] post-cascade: started code-server update poller
10:38:16.228 [telemetry] setup_step activate-editor fail: HTTP 200
10:38:16.713 [telemetry] error_screen activate-editor : HTTP 200
10:38:19.079 [focus] hd Focused(true)
10:38:22.746 [heartbeat] alive 510s
10:38:32.749 [heartbeat] alive 520s
10:38:42.751 [heartbeat] alive 530s
10:38:52.753 [heartbeat] alive 540s
10:39:02.756 [heartbeat] alive 550s
10:39:12.758 [heartbeat] alive 560s
10:39:22.761 [heartbeat] alive 570s
10:39:25.487 [focus] hd Focused(false)
10:39:32.763 [heartbeat] alive 580s
10:39:42.765 [heartbeat] alive 590s
10:39:52.767 [heartbeat] alive 600s
10:40:02.769 [heartbeat] alive 610s
10:40:09.982 [focus] hd Focused(true)
10:40:12.771 [heartbeat] alive 620s
10:40:22.775 [heartbeat] alive 630s
10:40:30.057 [focus] hd Focused(false)
10:40:32.779 [heartbeat] alive 640s
10:40:37.348 [focus] hd Focused(true)
10:40:42.781 [heartbeat] alive 650s
10:40:52.783 [heartbeat] alive 660s
10:41:00.745 [agents] skills: [] (default) nothing to do
10:41:02.786 [heartbeat] alive 670s
10:41:12.788 [heartbeat] alive 680s

5 Replies

John Lauer · 15d ago

Fernando, your logs show what is going on, and it is not a problem with your computer. On your PC, WSL's "mirrored" networking breaks the connection between Hydrogen and the editor inside your workspace. The other mode, "NAT", works.

Here is what happened in the log you sent:

  • Since Oct 21 your workspace was on mirrored networking, and the editor never finished loading.
  • This morning (around 08:13) the .wslconfig change you made with Claude switched WSL to NAT. After that the editor worked: its control port answered for over an hour, and the Claude sign-in reached your workspace.
  • At 09:39 you clicked "Restart WSL and try mirrored again" in the red box. That put WSL back on mirrored, and the editor has been stuck on the loading screen since.

That red box was our mistake. Your version of Hydrogen (1.0.666) shows it on every PC that runs NAT, even where sign-in works. The next version only shows it when sign-in actually fails.

To fix it now (about 2 minutes):

  1. Right-click the Hydrogen icon in the system tray (bottom right, near the clock) and choose Quit.
  2. Press Windows+R, type notepad %USERPROFILE%\.wslconfig and press Enter.
  3. Delete both networkingMode lines (the one starting with # and the networkingMode=mirrored line), and add this line under [wsl2]:
    networkingMode=nat
    
    Save and close Notepad.
  4. Open PowerShell and run: wsl --shutdown
  5. Open Adom Hydrogen from the Start menu.

Hydrogen respects networkingMode=nat when you set it yourself, so it will not switch you back. If the red box appears again, ignore it and do not click "Restart WSL and try mirrored again". On your PC, signing in to Claude works on NAT.

Please reply here and tell us whether the editor loads after that. We are also working on having Hydrogen notice when mirrored networking breaks the editor and switch to NAT by itself.

(This replaces adom/hydrogen#144, which I am closing so we keep one thread.)

John Lauer · 12d ago ·edited

Follow-up from the logs you sent: on your PC, WSL's mirrored networking keeps the editor from loading, and every mirrored attempt stopped at this step, while NAT networking got through setup in about 2 minutes. Hydrogen's automatic switch to NAT ran in a later step, so on your PC it never got the chance. Starting with 1.0.682, the editor step itself switches the PC to NAT once and tries again; you can switch back any time in Settings > Workspace networking. 1.0.682 is in testing now and will reach you through the normal update once it passes. If your Hydrogen already has Settings > Workspace networking (1.0.675 and later), choosing NAT there gets you past this step today.

John Lauer · 9d ago

Fernando, this is now public in Hydrogen 1.0.701: when mirrored networking keeps the editor from loading, the editor step switches the PC to NAT networking once and tries again, so setup gets through on PCs like yours. You can switch back any time in Settings, Workspace networking. It reaches you through the normal update. Everything else in this release: What's new in 1.0.701. Closing; reply here if setup stops again.

John Lauer closed this · 9d ago

it is now working @john!! Really appreciate the help for this. I will now continue my project using the app :))

John Lauer · 7d ago

Great to hear, Fernando. Thanks for sticking with it.

Log in to reply.