You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CERT_NOT_YET_VALID: certificate is not yet valid Attempt 9 - retrying in 3s #59733
Thanks for the report! CERT_NOT_YET_VALID means a server's TLS certificate looks like it isn't valid yet from your computer's point of view. A very common cause is a system clock or date that is wrong (set in the past), so please check that first. Another possible cause is a proxy, VPN or antivirus that inspects HTTPS traffic.
If your clock is correct and it still happens, could you share:
Your OpenCode version (opencode --version)
Your operating system and how you installed OpenCode
Which provider/model you were using, and what you were doing when the error appeared (e.g. sending a prompt, logging in, connecting an MCP server)
Whether you're behind a corporate proxy, VPN or antivirus that inspects HTTPS traffic
Any related log lines or a screenshot
You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.
These related issues may help (ordered by likelihood of being relevant):
fehler #59005: same CERT_NOT_YET_VALID error, closed without details
We haven't heard back, so we're closing this issue for now. Without your OpenCode version, operating system, provider/model and what you were doing when CERT_NOT_YET_VALID appeared, we can't tell what is causing it.
This error usually means your system clock or date is set in the past, or a proxy, VPN or antivirus is intercepting HTTPS traffic. Please check those first. If it still happens with a correct clock, open a new issue with those details and any related logs, and link back to #59733. Thanks!
Activity
opencodejr commentedon Oct 27, 2026
Thanks for the report!
CERT_NOT_YET_VALIDmeans a server's TLS certificate looks like it isn't valid yet from your computer's point of view. A very common cause is a system clock or date that is wrong (set in the past), so please check that first. Another possible cause is a proxy, VPN or antivirus that inspects HTTPS traffic.If your clock is correct and it still happens, could you share:
opencode --version)You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.
These related issues may help (ordered by likelihood of being relevant):
CERT_NOT_YET_VALIDerror, closed without detailsNODE_EXTRA_CA_CERTS) not picked up on Windowsopencodejr commentedon Oct 30, 2026
We haven't heard back, so we're closing this issue for now. Without your OpenCode version, operating system, provider/model and what you were doing when
CERT_NOT_YET_VALIDappeared, we can't tell what is causing it.This error usually means your system clock or date is set in the past, or a proxy, VPN or antivirus is intercepting HTTPS traffic. Please check those first. If it still happens with a correct clock, open a new issue with those details and any related logs, and link back to #59733. Thanks!