Setup job

[igrebnev]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

Hello!

I am experiencing a persistent issue with my self-hosted GitHub Actions runner.

When running any workflow that uses actions (e.g., actions/checkout@v4), the job fails at the "Set up job" step with the error:
"Failed to resolve action download info."

To diagnose, I tried accessing https://marketplace.actions.githubusercontent.com from:

• My server (self-hosted runner)
• Multiple VPNs (different countries/providers)
• Mobile internet
• Tor network
• With different User-Agents

In all cases, I receive an HTTP 400 response with the message:
"Our services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."

This means the issue is not related to my IP address, provider, or User-Agent.

• GitHub Status (https://www.githubstatus.com/) shows all systems operational.
• The issue persists for several hours.
• My test workflows that do not use any actions (just shell commands) work fine.
• The problem occurs before any workflow steps are executed, at the action download phase.

Example curl output:

• Host marketplace.actions.githubusercontent.com:443 was resolved.
• IPv6: 2620:1ec:21::16
• IPv4: 13.107.42.16
• Trying 13.107.42.16:443...
• Connected to marketplace.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 (IN), TLS handshake, CERT verify (15):
• TLSv1.3 (IN), TLS handshake, Finished (20):
• TLSv1.3 (OUT), TLS handshake, Finished (20):
• SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / secp521r1 / RSASSA-PSS
• ALPN: server accepted h2
• Server certificate:
• subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=*.actions.githubusercontent.com
• start date: May 22 00:00:00 2025 GMT
• expire date: May 21 23:59:59 2026 GMT
• subjectAltName: host "marketplace.actions.githubusercontent.com" matched cert's "*.actions.githubusercontent.com"
• issuer: C=US; O=DigiCert Inc; CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
• SSL certificate verify ok.
• Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
• Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
• Certificate level 2: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
• using HTTP/2
• [HTTP/2] [1] OPENED stream for https://marketplace.actions.githubusercontent.com/
• [HTTP/2] [1] [:method: GET]
• [HTTP/2] [1] [:scheme: https]
• [HTTP/2] [1] [:authority: marketplace.actions.githubusercontent.com]
• [HTTP/2] [1] [:path: /]
• [HTTP/2] [1] [user-agent: Mozilla/5.0]
• [HTTP/2] [1] [accept: /]

GET / HTTP/2
Host: marketplace.actions.githubusercontent.com
User-Agent: Mozilla/5.0
Accept: /

• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  < HTTP/2 400
  < x-msedge-ref: 0nKx2aAAAAAASIQ4gQ7E/SK7oiA0VHX1/V0FXMDFFREdFMDYyMgBFZGdl
  < date: Tue, 15 Jul 2025 19:31:39 GMT
  <
• Connection #0 to host marketplace.actions.githubusercontent.com left intact

Our services aren't available right now

We're working to restore all services as soon as possible. Please check back soon.

0nKx2aAAAAAASIQ4gQ7E/SK7oiA0VHX1/V0FXMDFFREdFMDYyMgBFZGdl%

Could you please check if there are any issues with the Actions Marketplace or CDN for my region?
Is this a known issue, and is there any workaround?

Thank you!

[igrebnev]

Anybody help please

[igrebnev]

I made it. But I l make it again.

[igrebnev]

Maybe delete all project and start from scratch? Joke

[igrebnev]

Thank you for your suggestions!
I have already tried the following steps:
Completely removed and reinstalled the self-hosted runner using a fresh config.sh.
Tried running the workflow from different networks, devices, and IPs (including multiple VPNs, mobile internet, and even Tor).
Used different User-Agents for curl requests.
The issue persists everywhere: I always get HTTP 400 with "Our services aren't available right now" from https://marketplace.actions.githubusercontent.com.
Test workflows that do not use any actions (just shell commands) work fine.
The problem occurs before any workflow steps are executed, at the action download phase.
GitHub-hosted runners work fine for the same workflow.
So, it seems the problem is not related to my runner, configuration, or IP address.
I will try to contact GitHub Support as you suggested, but if anyone else is experiencing the same issue or has found a workaround, please share!
Thanks again for your help!