Linux self-hosted runners offline since 2026-11-06 01:38 UTC: NotTimeValid on broker.actions.githubusercontent.com (Let's Encrypt YR1 / Root YR chain), same as #4560

Aperta
#4,838 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp, github-actions, linux
Ambito
devops, networking

Direzione di ricerca

Start by comparing this failure with issue #4560 and trace the BrokerMessageListener connection setup in the runner. Reproduce certificate validation with the reported Linux and .NET environment, then identify why SslStream rejects the served chain as NotTimeValid while OpenSSL accepts it. Done means new broker connections succeed with normal TLS verification and the runner remains online.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Since about 2026-11-06 01:38 UTC, self-hosted runners on Linux cannot create a session with broker.actions.githubusercontent.com. Every attempt fails in BrokerMessageListener with:

System.Security.Authentication.AuthenticationException: The remote certificate is invalid because of errors in the certificate chain: NotTimeValid

The runner shows as offline in GitHub and jobs stay queued. This looks like the same failure as #4560 (July 2026, macOS), now on Linux. Runners that already had an open connection kept working until that connection dropped; every new connection fails, including after restarting the service.

What changed on the server side

broker.actions.githubusercontent.com presented a newly issued certificate (leaf notBefore 2026-11-05 23:35:54 UTC):

0: CN=*.actions.githubusercontent.com  notBefore Nov  5 23:35:54 2026 GMT, notAfter Feb  3 23:35:53 2027 GMT
1: C=US, O=Let's Encrypt, CN=YR1        notBefore Sep  3 2025,               notAfter Sep  2 2028
2: C=US, O=ISRG, CN=Root YR             (cross-signed by ISRG Root X1) notBefore May 13 2026, notAfter Sep 2 2032

pipelines.actions.githubusercontent.com and vstoken.actions.githubusercontent.com still serve an older certificate (issuer YR2, notBefore Oct 14 2026).

Environment

  • Runner 2.338.2 (latest release), linux-x64, Ubuntu 24.04.5 LTS under WSL2
  • OpenSSL 3.0.13, ca-certificates 20260816ubuntu0.24.04.1
  • No proxy. System clock verified correct: it matches the Date header returned by the server to the second.
  • Three runners on the same machine fail identically.

Diagnosis (the OS trust and the network are healthy)

  1. curl and openssl s_client (IPv4 and IPv6, repeated 5 times each) connect and report Verify return code: 0 (ok).
  2. openssl verify -x509_strict -untrusted <served intermediates> <leaf> is OK. With -attime set to the present it is OK.
  3. No expired certificates exist in /etc/ssl/certs.
  4. Restarting the runner service does not help.
  5. Adding the official self-signed ISRG Root YR (from letsencrypt.org/certs/gen-y/root-yr.pem; its subject key identifier matches the served cross-signed certificate) to the system trust store and restarting does not help. Reverted afterwards.

So OpenSSL validates the served chain, but the runner's bundled .NET SslStream rejects it with NotTimeValid. This is the same pattern reported in #4560.

Impact

All self-hosted runners that are routed to the edge serving this certificate and have to open a new connection go offline, and all jobs stay queued. There is no client-side workaround other than disabling TLS verification, which should not be used.

Ask

  • Could the team confirm whether this is the same underlying cause as #4560 and what the fix was then?
  • A fix on the service side (certificate or chain) or a runner/.NET fix that handles this chain.
Lingua principale
C#
Stelle
6.4k
Fork
1.5k
Merge medio
1g 7h
PR unite (30g)
36

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di actions/runner

Tutte le issue di actions/runner

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.