[v2 Windows] v2.0.3 times out waiting for background service after local CLI install #49034

Activity

1. opencode-agent

   added

   2.0

   on Sep 14, 2026
2. github-actions

   assigned

   Hona

   on Sep 14, 2026
3. github-actions commented on Sep 14, 2026

   

   github-actionsBot

   on Sep 14, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [v2 Windows] opencode2 hangs at "Starting background server..." after reinstall #41746: opencode2 hangs at "Starting background server..." after reinstall (Windows, v2 — same symptom)
   • opencode2 became stuck starting its managed background server #41696: opencode2 became stuck starting its managed background server (same root failure)

   Since you already mention these in your report, it would be worth confirming whether your reproduction matches those issues exactly. If so, adding your details as a comment there (with the v2.0.3 version info) would help consolidate tracking.
4. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the report! I think this is a duplicate of #41746, the existing Windows report of opencode2 stopping at "Starting background server..." and then timing out.

   Possible duplicates and related issues, ordered from most to least likely:

   • [v2 Windows] opencode2 hangs at "Starting background server..." after reinstall #41746: same Windows symptom and the same timeout error. A commenter there traced it to Windows reserving a range of ports (Hyper-V / WSL2 / Docker) that includes the default service port 49374.
   • opencode2 became stuck starting its managed background server #41696: on older builds the real startup error (usually "port already in use") was hidden behind this generic timeout. Marked fixed in v2.0.23, which now reports the actual error.
   • service: hardcoded default port 49374 with no fallback and a silent hang when it's unavailable #52234 / service: hardcoded default port 49374 locks out any second client on shared loopback (multi-user/WSL mirrored), surfacing only a generic timeout #50672: the default port 49374 is hardcoded with no fallback, so a conflict shows up only as a timeout.

   Things that may help in the meantime:

   1. Check whether Windows has reserved the port:

      netsh interface ipv4 show excludedportrange protocol=tcp

      If 49374 falls inside a listed range, move the service to a free port:

      opencode2 service set port 40900
      opencode2 service start

   2. Look for the underlying error in %USERPROFILE%\.local\share\opencode\log\opencode.log, or upgrade to v2.0.23 or later, which should print the real error instead of the timeout.

   The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different, for example if a newer version or the log shows an error other than the port conflict.
5. opencodejr

   added

   pending close

   triaging

   on Oct 28, 2026
6. opencodejr

   closed this as duplicateon Oct 29, 2026
7. opencodejr commented on Oct 29, 2026

   

   opencodejrBot

   on Oct 29, 2026

   Contributor

   More actions

   We haven't heard back since the duplicate note yesterday, so I'm closing this as a duplicate of #41746. That issue tracks the same Windows problem: opencode2 stops at "Starting background server..." and then times out.

   If you still hit this, it's worth checking two things first:

   • Reserved ports: see whether Windows has reserved a port range that includes 49374 with netsh interface ipv4 show excludedportrange protocol=tcp. If it has, move the service to a free port with opencode2 service set port <port>.
   • v2.0.23 or later: this version reports the actual startup error instead of the generic timeout (opencode2 became stuck starting its managed background server #41696).

   If a newer version or opencode.log shows a different underlying error, please comment here or on #41746 and we can reopen. Thanks for the report!