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

オープン
#4,838 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
42/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp, github-actions, linux
領域
devops, networking

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
C#
スター
6.4k
フォーク
1.5k
平均マージ
1日 7時間
マージ済み PR(30日)
36

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

actions/runner のほかの issue

actions/runner の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。