CLI: web and serve show generic error message when the port is already in use #46263

Activity

1. github-actions

   assigned

   jlongster

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

   

   github-actionsBot

   on Aug 30, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • Steps to reproduce is empty — please describe how to trigger this error (e.g. which command you ran, whether a port was already occupied, etc.)
   • OpenCode version is empty — please provide the version you were using
   • Operating System and Terminal are empty — these help narrow down environment-specific issues
   • The description contains only a screenshot with no textual context; please add a brief written description of what you observed and what you expected

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

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

   • opencode serve: bind failures print bare "Unexpected error / ServeError" — the listen errno is never surfaced #38738: opencode serve bind failures print bare "Unexpected error / ServeError" — the listen errno is never surfaced (same root cause: port-in-use errors show a generic, unhelpful message)
   • opencode serve: Bun collapses every listen() errno to EADDRINUSE, so a bad --hostname is misdiagnosed as a port conflict #38739: companion issue on Bun collapsing every listen() errno to EADDRINUSE

   If you believe this was flagged incorrectly, please let a maintainer know.
3. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   and removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Aug 30, 2026
4. github-actions commented on Aug 30, 2026

   

   github-actionsBot

   on Aug 30, 2026 – with GitHub Actions

   Contributor

   More actions

   Thank you for updating the issue! It now includes a clear description, steps to reproduce, a screenshot, your OpenCode version, OS, and terminal info. Everything looks good — the needs:compliance label has been removed.
5. ling9ling7 commented on Sep 28, 2026

   

   ling9ling7

   on Sep 28, 2026

   More actions

   Related (Windows-specific, different root cause): #51899 — same bare Unexpected error / ServeError, but in my case the port is held by an orphaned socket whose owning PID no longer exists (netstat shows a LISTENING entry, tasklist shows no such process), so there is no listener to kill and only a reboot clears it. Includes a raw TcpListener bind test proving the WSAEADDRINUSE, plus a suggestion to detect and report this state explicitly.
6. thdxr commented on Oct 11, 2026

   

   thdxr

   on Oct 11, 2026

   Member

   More actions

   Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.

   — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
7. thdxr

   closed this as not plannedon Oct 11, 2026