[v2 Windows] opencode2 hangs at "Starting background server..." after reinstall #41746

Activity

1. github-actions

   assigned

   Hona

   on Aug 11, 2026
2. github-actions commented on Aug 11, 2026

   

   github-actionsBot

   on Aug 11, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • opencode2 became stuck starting its managed background server #41696: Similar symptom — opencode2 hangs at "Starting background server..." / stuck starting its managed background server (different root cause suspected: port conflict vs. Windows reinstall, but the failure mode is the same)

   If your issue is distinct from #41696, feel free to add that context to help maintainers differentiate them.
3. opencode-agent

   added

   2.0

   on Aug 11, 2026
4. opencode-agent commented on Aug 11, 2026

   

   opencode-agentBot

   on Aug 11, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report. Could you reproduce this once more and share the relevant log output?

   On Windows, the installed-build log is at:

   %USERPROFILE%\.local\share\opencode\log\opencode.log
   

   Please redact API keys, authorization headers, prompts, file contents, and any other sensitive data before sharing it.
5. Double77x commented on Sep 7, 2026

   

   Double77x

   on Sep 7, 2026

   More actions

   Ran into this on Windows. In my case the timeout was caused by a port collision with Windows dynamic port reservations. On Windows, especially with Hyper-V, WSL2 or Docker installed it likes to reserve large blocks of ports.

   The CLI hung and eventually threw:

   • Error: Timed out waiting for the background service to start

   Checking ~/.local/share/opencode/log/opencode.log showed the actual error:

   • Managed service port 49374 on 127.0.0.1 is already in use by another process.

   Running netsh interface ipv4 show excludedportrange protocol=tcp confirmed that Hyper-V/WSL had reserved ports
   49336 to 49435, preventing the background service from binding to 49374.

   Setting an unreserved port resolved it: powershell opencode service set port 40900 opencode service start

   Two improvements would probably help here:

   1. Surface stderr from the background service in the CLI rather than silently waiting for the timeout.
   2. Retry with an alternate port (or request port 0 and persist what the OS assigns) when hitting EADDRINUSE / WSAEACCES.

   👍React with 👍1Reacted by celery
6. Double77x

   added a commit that references this issue on Sep 7, 2026

   fix(cli): resolve background service port collision on Windows

   ...

   This issue will close once commit 7487028 is merged into the 'dev' branch.

   7487028
7. humb1t commented on Sep 16, 2026

   

   humb1t

   on Sep 16, 2026

   More actions

   I get same issue on linux machine today
8. laundry-96 commented on Oct 7, 2026

   

   laundry-96

   on Oct 7, 2026

   More actions

   I'm getting the same issue. I have multiple users on my server, so the port can be blocked by other people
9. luzdealba commented on Oct 12, 2026

   

   luzdealba

   on Oct 12, 2026

   More actions

   I had the same issue on WSL after upgrading from v1 to v2 via opencode upgrade --major, even after fully uninstalling and reinstalling via NPM

   In the end, I fully (re)uninstalled and installed via curl -fsSL https://opencode.ai/v2/install | bash — and it worked.

   Seems like the upgrade and NPM or PNPM installations aren't v2-ready yet.

   👍React with 👍2Reacted by Victor Safronov and Dan Leslie