Registry certificate is invalid

35 views
Skip to first unread message

Christian

unread,
11:59 AM (5 hours ago) 11:59 AM
to bazel-discuss
Hello,

builds started failing, and chrome displays an error as well, it seems that https://bcr.bazel.build/ certificate is expired?

Best,

Xudong Yang

unread,
3:44 PM (2 hours ago) 3:44 PM
to Christian, bazel-discuss
This has been resolved -- please see https://github.com/bazelbuild/bazel/issues/28101#issuecomment-3693346788 for a brief explanation of the outage. There will be a postmortem.

"  YÁNG Xùdōng (杨旭东)
#  SURNAME Givenname
=  Software Engineer
@  Google New York


--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bazel-discuss/CAEffnibqkNqqTitSXjvecZhBdbLAZYeNNKPXt0kTsTb0Cqrg%3DA%40mail.gmail.com.

Ming Zhao

unread,
5:12 PM (5 minutes ago) 5:12 PM
to bazel-discuss
Actually all bazel.build certs seem to have expired:

2025/12/26 17:29:29 could not download Bazel: failed to download bazel: failed to download bazel: HTTP GET https://releases.bazel.build/8.5.0/release/bazel-8.5.0-linux-x86_64 failed: unable to complete 5 requests to https://releases.bazel.build/8.5.0/release/bazel-8.5.0-linux-x86_64 within 30s. Most recent failure: Get "https://releases.bazel.build/8.5.0/release/bazel-8.5.0-linux-x86_64": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2025-12-26T17:29:29Z is after 2025-12-26T08:35:39Z

John Field

unread,
5:12 PM (5 minutes ago) 5:12 PM
to bazel-discuss
Hi folks,

We're aware of the issue with expired certificates. Normally, these are auto-renewed, but something obviously failed in this case. Working on a manual fix now.

-John (on behalf of the Bazel Team

Ming Zhao

unread,
5:12 PM (5 minutes ago) 5:12 PM
to bazel-discuss
workaround:
On Friday, December 26, 2025 at 8:59:38 AM UTC-8 christian...@gmail.com wrote:
Reply all
Reply to author
Forward
0 new messages