GitHub Actions @actions/artifact Upload Fails with ACTIONS_RUNTIME_TOKEN Missing via HTTPS Proxy

What this error means

@actions/artifact BlobClient upload fails with "Bad Request" through HTTPS proxy — no proxy transport configured; artifact.uploadArtifact Fails with Unable to get the ACTIONS_RUNTIME_TOKEN env variable is a GitHub Actions failure pattern reported for developers trying to fix github actions artifact upload failures caused by missing proxy transport configuration and missing actions_runtime_token environment variable in ci/cd workflows. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Two distinct but related issues on actions/toolkit: #2377 (BlobClient Bad Request via HTTPS proxy, Apr 2026) and #2009 (ACTIONS_RUNTIME_TOKEN missing). Both affect enterprise users behind corporate proxies. Blocks CI/CD pipeline completions. Maps to GitHub Actions per approved categories.

Common causes

• Two distinct but related issues on actions/toolkit: #2377 (BlobClient Bad Request via HTTPS proxy, Apr 2026) and #2009 (ACTIONS_RUNTIME_TOKEN missing). Both affect enterprise users behind corporate proxies. Blocks CI/CD pipeline completions. Maps to GitHub Actions per approved categories.

Quick fixes

1. Confirm the exact error signature matches @actions/artifact BlobClient upload fails with "Bad Request" through HTTPS proxy — no proxy transport configured; artifact.uploadArtifact Fails with Unable to get the ACTIONS_RUNTIME_TOKEN env variable.
2. Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/actions/toolkit/issues/2377
• https://github.com/actions/toolkit/issues/2009

Evidence note: Two distinct but related issues on actions/toolkit: #2377 (BlobClient Bad Request via HTTPS proxy, Apr 2026) and #2009 (ACTIONS_RUNTIME_TOKEN missing). Both affect enterprise users behind corporate proxies. Blocks CI/CD pipeline completions. Maps to GitHub Actions per approved categories.

Related errors

• GitHub Actions

FAQ

What should I check first?

Start with the exact @actions/artifact BlobClient upload fails with "Bad Request" through HTTPS proxy — no proxy transport configured; artifact.uploadArtifact Fails with Unable to get the ACTIONS_RUNTIME_TOKEN env variable text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed GitHub Actions workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without @actions/artifact BlobClient upload fails with "Bad Request" through HTTPS proxy — no proxy transport configured; artifact.uploadArtifact Fails with Unable to get the ACTIONS_RUNTIME_TOKEN env variable.