GitHub Actions / GitHub Actions

GitHub Actions Runner Proxy Upload Stall Through HTTPS_PROXY

Fix GitHub Actions self-hosted runner stalling on Azure Blob uploads when HTTPS_PROXY is configured Includes evidence for GitHub Actions troubleshooting demand.

Source-backed Last updated May 15, 2026 1 source Needs local verification

Category: GitHub Actions
Error signature: Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 15, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Actions, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport is a GitHub Actions failure pattern reported for developers trying to fix github actions self-hosted runner stalling on azure blob uploads when https_proxy is configured. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Filed 2026-04-15. Runner's ResultsHttpClient creates BlobClient without HttpClientTransport proxy config. Azure SDK falls back to default transport ignoring HTTPS_PROXY. Causes 75-second stalls and timeouts on all artifact uploads.

Common causes

Self-hosted runners configured with HTTPS_PROXY experience 75-second stalls on Azure Blob Storage uploads (logs, summaries, artifacts). The BlobClient ignores proxy transport configuration. Affects all enterprises using proxy servers for CI/CD.
Filed 2026-04-15. Runner's ResultsHttpClient creates BlobClient without HttpClientTransport proxy config. Azure SDK falls back to default transport ignoring HTTPS_PROXY. Causes 75-second stalls and timeouts on all artifact uploads.

Quick fixes

Confirm the exact error signature matches Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport.
Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
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

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
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.

Diagnostic flow for this page

Match Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport exactly before applying the quick fix.
Compare the failing environment with GitHub Actions versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport mean in GitHub Actions?

Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport indicates the workflow described by "GitHub Actions Runner Proxy Upload Stall Through HTTPS_PROXY" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport?

Check whether this cause matches your environment: Self-hosted runners configured with HTTPS_PROXY experience 75-second stalls on Azure Blob Storage uploads (logs, summaries, artifacts). The BlobClient ignores proxy transport configuration. Affects all enterprises using proxy servers for CI/CD.

Is the Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport guidance source-backed?

The "GitHub Actions Runner Proxy Upload Stall Through HTTPS_PROXY" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport?

For "GitHub Actions Runner Proxy Upload Stall Through HTTPS_PROXY", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Runner Azure Blob uploads stall through HTTPS proxy - BlobClient not configured with proxy transport?

For "GitHub Actions Runner Proxy Upload Stall Through HTTPS_PROXY", collect the failing GitHub Actions command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.