Unable to connect to the first certificate #40314

Activity

1. github-actions

   assigned

   kitlangton

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

   

   github-actionsBot

   on Aug 3, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • Steps to reproduce are missing — please describe exactly what you did that triggered the error
   • OpenCode version is missing — run opencode --version and include the output
   • Operating System is missing — please specify your OS and version
   • Terminal is missing — please specify which terminal you are using
   • The description lacks enough detail to diagnose the problem (e.g., which provider/model are you using, exact error message text)

   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:

   • Self-signed TLS certificate no longer working with 1.17.12+ #35365: Self-signed TLS certificate no longer working (similar certificate connection error)
   • Error: unknown certificate verification error #8601: Error: unknown certificate verification error (same error category)
   • [UX] Improve "unknown certificate verification error" with actionable guidance for network/proxy failures #36590: Improve "unknown certificate verification error" with actionable guidance for network/proxy failures
   • Certificate verification errors bypass session retry #37884: Certificate verification errors bypass session retry

   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 3, 2026
4. github-actions commented on Aug 3, 2026

   

   github-actionsBot

   on Aug 3, 2026 – with GitHub Actions

   Contributor

   More actions

   Thank you for updating the issue! It now has the key information needed (description, OS, terminal, and version). We appreciate you taking the time to fill this out.
5. myacoub91 commented on Aug 3, 2026

   

   myacoub91

   on Aug 3, 2026

   More actions

   @papakojo16, I had the same issue a couple of days ago, I am using mac here are the steps I followed to get it solved
   The root cause was DNS filtering by Whalebone on my network. My router DNS was resolving opencode.ai to a private sinkhole IP (10.X.X.X) and serving a fake certificate issued by Whalebone Sinkhole CA instead of the real certificate.

   Fix:

   Changed my Mac DNS settings from the router DNS (192.168.0.1) to Cloudflare DNS (1.1.1.1 / 1.0.0.1)
   Flushed the DNS cache
   Verified that opencode.ai now resolves to the correct Cloudflare IPs and uses a valid Google Trust Services certificate

   After the DNS change, both HTTPS access and the OpenCode CLI worked normally.
6. papakojo16 commented on Aug 3, 2026

   

   papakojo16

   on Aug 3, 2026 via email

   Author

   More actions

   Thank you for your Response 🙏, I am really grateful for your help. I will contact you again if need any further assistance

   …

   On Mon, Aug 3, 2026, 9:02 PM Mina Yacoub ***@***.***> wrote: *myacoub91* left a comment (anomalyco/opencode#40314) <#40314 (comment)> @papakojo16 <https://github.com/papakojo16>, I had the same issue a couple of days ago, I am using mac here are the steps I followed to get it solved The root cause was DNS filtering by Whalebone on my network. My router DNS was resolving opencode.ai to a private sinkhole IP (10.X.X.X) and serving a fake certificate issued by Whalebone Sinkhole CA instead of the real certificate. *Fix:* Changed my Mac DNS settings from the router DNS (192.168.0.1) to Cloudflare DNS (1.1.1.1 / 1.0.0.1) Flushed the DNS cache Verified that opencode.ai now resolves to the correct Cloudflare IPs and uses a valid Google Trust Services certificate After the DNS change, both HTTPS access and the OpenCode CLI worked normally. — Reply to this email directly, view it on GitHub <#40314?email_source=notifications&email_token=BQEWNJ3OO2NLAC77VGNBR7L5ID4WDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJXGE3DONBWGM3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5171674636>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQEWNJ2Y6J5EP3REUPLM5Y35ID4WDAVCNFSNUABFKJSXA33TNF2G64TZHM4TONJXGM2DGMJZHNEXG43VMU5TKMBVGM3TCOBTGAYKC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BQEWNJ4RAI7B7D6VTDCQ2WD5ID4WDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJXGE3DONBWGM3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BQEWNJ7CMZTE2JMV7NM4CB35ID4WDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJXGE3DONBWGM3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>
7. github-actions commented on Oct 4, 2026

   

   github-actionsBot

   on Oct 4, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
8. github-actions

   closed this as not plannedon Oct 4, 2026