Repository navigation
OpenCode: Failed to fetch... #28424
Description
Description
OpenCode suddenly stopped working, showing "Failed to fetch" when sending messages. It was working normally before, then suddenly failed one day.
The log shows as pictured:
- Failed to load resource: net::ERR_CONNECTION_REFUSED
- GET http://127.0.0.1:XXXXX/global/health net::ERR_CONNECTION_REFUSED
- [global-sdk] event stream error: TypeError: network error
Port keeps changing (49344, 51008, 52410, 52764, 59261, etc.), indicating local service never started successfully.
Already uninstalled and reinstalled, problem persists.
Event Before Problem Occurred
Before the error appeared, I was configuring OpenCode's MCP (Model Context Protocol), asking OpenCode to write a JSON script for listening and automatically recording conversations.
Suspected Cause
MCP configuration may have written incorrect JSON or config, causing hilo runtime to crash at startup.
Plugins
No response
OpenCode version
- OpenCode version: v24.14.1
- OS: Windows 11 (AMD64)
- Network: China mainland network, tried both proxy (global mode) and direct connection, neither works
Steps to reproduce
- OpenCode was working normally
- Configured MCP, asked OpenCode to write JSON script for auto-recording conversations
- OpenCode suddenly showed "Failed to fetch"
- Uninstalled and reinstalled OpenCode
- Error persists, hilo runtime still not starting
Screenshot and/or share link
Operating System
No response
Terminal
No response
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon May 20, 2026
This issue does not fully meet our contributing guidelines.
What needs to be fixed:
opencode --versionand include itPlease edit this issue to address the above within 2 hours, or it will be automatically closed.
If you believe this was flagged incorrectly, please let a maintainer know.
[-]OpenCode: Failed to match...[/-][+]OpenCode: Failed to fetch...[/+]github-actions commentedon May 20, 2026
Thanks for updating the issue! It now includes all the required information — a clear description of the problem, steps to reproduce, version details, and screenshots. We appreciate you taking the time to fill this out properly.
github-actions commentedon Jul 20, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
Ceegore commentedon Aug 14, 2026
I runto into the same issue. This makes the tool almost unusable. After like 30mins of work, it just starts to stop with "Failed to fetch" and requires a tool restart to work again.