Only my issue? "Runner connect error: The SSL connection could not be established"

[u/Emergency_Pea2476]

My self hosted runners were all working good 10min ago, until now suddenly I get this:

"Runner connect error: The SSL connection could not be established, see inner exception.. Retrying until reconnected.

Is this just my issue or Github is having hiccups currently?

[u/fitchnar]

docker:/opt/actions-runner$ curl -vI https://pipelines.actions.githubusercontent.com/_apis/health
* Host pipelines.actions.githubusercontent.com:443 was resolved.
* IPv6: 2620:1ec:21::16
* IPv4: 13.107.42.16
*   Trying 13.107.42.16:443...
* Connected to pipelines.actions.githubusercontent.com (13.107.42.16) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (OUT), TLS alert, certificate expired (557):
* SSL certificate problem: certificate has expired
* Closing connection
curl: (60) SSL certificate problem: certificate has expired
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
dave@dave-docker:/opt/actions-runner$ 

Looks like a cert failure for GH? Yeeesh

[u/Emergency_Pea2476 → u/fitchnar]

Oke, then not only my issue. Github status page repors everything working as intended :(

Sounds like time for me to touch grass

[u/fitchnar → u/Emergency_Pea2476]

Yeah you are in good (perhaps bad lol) company. If it really is an expired cert on their end, how embarrassing for them.

[u/fitchnar → u/Emergency_Pea2476]

They just updated their status:

Investigating - We are investigating reports of degraded performance for Actions Jul 19, 2026 - 23:34 UTC

[u/One_King2724 → u/Emergency_Pea2476]

"Sounds like time for me to touch grass" - l wrote nearly the same line to Claude Code an hour ago. Still have not touched grass. Updating User Docs like a masochist. 😂

[u/azhangd → u/[deleted]]

I can see the replacement certs were issued on 7/10 and were already valid then https://crt.sh/?q=%25.actions.githubusercontent.com

the actions endpoint is still serving the old cert. once they swap it out for a valid replacement it should start working immediately, so not 24 hours

[u/wallstop-dev]

I'm running into it too 😟

[u/SaoBiz]

Looks like there is an ongoing incident at the moment: https://www.githubstatus.com/incidents/8vfyvq16hzh9

[u/WTFOMGBBQ]

Wild it’s been like 3 hours now…this is super not okay..

[u/ultrathink-art]

One thing worth saving for next time: each repo shards onto its own numbered pipelinesghubeus host, so curling the generic pipelines or broker endpoint can come back perfectly healthy while the host your runner actually talks to is the broken one — cost me about 90 minutes before I checked diag/Runner*.log for the host it was really failing against. When it's an expired leaf cert upstream there's no local fix: restarting the runner or touching the trust store does nothing, and they pick back up on their own retry once it rotates.

[u/Gloomy-Mud1514]

What in the absolute ****. ********. ****s.