Answer: Run `opencode api get /api/info` to check that the CLI can reach the background service; a successful health response verifies the local client-to-service connection. Then run a normal provider request to verify the service's outbound proxy and certificate path. Status: Overdue (check was due 2026-11-20T13:37:05Z and has not succeeded) Entry: tool/opencode/troubleshooting/verify-network-config Revision: 2 Digest: sha256:579cd907f19503fa (changes whenever the content changes) Timeline: Created: 2026-11-13T03:57:55Z Last changed: 2026-11-14T13:44:31Z (proxy verification: — → Run a normal provider request to verify the service’s outbound proxy and certificate path.) Last verified: 2026-11-19T13:37:05Z Next check: 2026-11-20T13:37:05Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of health check command | opencode api get /api/info | [1] | 2026-11-19 local connection verification | A successful health response verifies the local client-to-service connection. | [1] | 2026-11-19 proxy verification | Run a normal provider request to verify the service’s outbound proxy and certificate path. | [1] | 2026-11-19 Sources: [1] opencode. "Network | OpenCode". https://opencode.ai/docs/network/ Role: primary. Accessed: 2026-11-19T13:37:05Z Quote: "opencode api get /api/info" (Supports: health check command) Quote: "A successful health response verifies the local client-to-service connection." (Supports: local connection verification) Quote: "Run a normal provider request to verify the service’s outbound proxy and certificate path." (Supports: proxy verification) Snapshot SHA-256: 3056c50c33d3ed158df7cc3a765c06e9fea94934acf0a36506414878cc4ec08f (captured 2026-11-13T13:31:04Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T13:31:06Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:37:05Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:37:05Z Last attempt: 2026-11-19T13:37:05Z Notes and limitations: Extracted automatically from a single official source (section "Verify"). Related: https://latestn.com/tool/opencode/troubleshooting/verify-ported-plugin How do I verify a ported opencode plugin works in V2? https://latestn.com/tool/opencode/troubleshooting/web-ui-over-ssh How do I access the opencode web UI over SSH? https://latestn.com/tool/windsurf/account-and-plans/cancel-paid-plan How do I cancel my paid Windsurf plan? https://latestn.com/tool/opencode/troubleshooting/loopback-no-proxy-requirement Why does opencode require loopback addresses in NO_PROXY when a proxy is configured? https://latestn.com/tool/opencode/troubleshooting/raycast-free-models-403 Why do free-tier chat models return HTTP 403 in Raycast with OpenCode? https://latestn.com/tool/opencode/troubleshooting/read-logs How do I read opencode logs to debug an issue? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-14T13:44:31Z | changed | proxy verification: — → Run a normal provider request to verify the service’s outbound proxy and certificate path. | [1] 2026-11-14T13:44:31Z | changed | local connection verification: — → A successful health response verifies the local client-to-service connection. | [1] 2026-11-14T13:44:31Z | changed | health check command: — → opencode api get /api/info | [1] 2026-11-14T13:44:31Z | changed | proxy verification step: Run a normal provider request to verify the service’s outbound proxy and certificate path. → — | [1] 2026-11-14T13:44:31Z | changed | health check purpose: A successful health response verifies the local client-to-service connection. → — | [1] 2026-11-14T13:44:31Z | changed | verification command: opencode api get /api/info → — | [1] 2026-11-13T03:57:55Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/opencode/troubleshooting/verify-network-config/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/opencode/troubleshooting/verify-network-config POST: https://latestn.com/dispute/tool/opencode/troubleshooting/verify-network-config with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/opencode/troubleshooting/verify-network-config?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I verify that opencode's network and proxy configuration is working? Revision 2, last verified 2026-11-19T13:37:05Z. https://latestn.com/tool/opencode/troubleshooting/verify-network-config (accessed 2026-11-21T09:53:35Z). @misc{LatestN_tool_opencode_troubleshooting_verify_network_config_r2, title = {How do I verify that opencode's network and proxy configuration is working?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/opencode/troubleshooting/verify-network-config}}, note = {Revision 2; digest sha256:579cd907f19503fa; last verified 2026-11-19T13:37:05Z; accessed 2026-11-21T09:53:35Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/opencode/troubleshooting/verify-network-config