Deployment Failed: Downloading the Resource Package
How to fix deployment failures during the resource package download step when setting up ComfyUI, especially when GitHub downloads time out or your proxy path is incomplete.
If the launcher stops at Downloading resource package, first-run deployment could not finish downloading the managed install payload from GitHub or another upstream host. This is not a ComfyUI problem yet — the environment never reached a stable installed state. Solve the download path before repairing Python packages or plugins.
The most common blockers:
- Network restrictions — direct GitHub connections can be slow with high packet loss, timing out large downloads
- Proxy misconfiguration — a proxy tool (Clash, v2rayN) is running but the system or Git is not routing through it
- Firewall blocking — corporate or school networks block GitHub domains
- Insufficient disk space — at least 5 GB free is required on the install drive
Fastest triage order
- Confirm the proxy tool is really running.
- Confirm the launcher proxy is set correctly.
- Test whether GitHub loads and downloads normally on the same machine.
- Check disk space on the target drive.
- Retry after fixing only one blocker at a time.
Option 1: Configure a proxy in Wonderful Launcher (recommended)
If you already use a proxy tool (Clash, v2rayN, Shadowrocket), tell Wonderful Launcher to route through it: open Settings → Network Proxy, enter your proxy address, then retry.
| Proxy tool | HTTP proxy address | SOCKS5 proxy address |
|---|---|---|
| Clash / Clash Verge | http://127.0.0.1:7890 | socks5://127.0.0.1:7891 |
| v2rayN | http://127.0.0.1:10809 | socks5://127.0.0.1:10808 |
| Shadowsocks | http://127.0.0.1:1080 | socks5://127.0.0.1:1080 |
The ports above are defaults. Check your proxy tool for the actual ports.
Option 2: Set system environment variables
If Option 1 does not work, set proxy variables at the system level.
Temporary (current PowerShell session):
$env:HTTP_PROXY = "http://127.0.0.1:7890"
$env:HTTPS_PROXY = "http://127.0.0.1:7890"Or in CMD:
set HTTP_PROXY=http://127.0.0.1:7890
set HTTPS_PROXY=http://127.0.0.1:7890Replace 7890 with your proxy's actual port.
Permanent: Win + R → sysdm.cpl → Advanced → Environment Variables. Under User variables, add HTTP_PROXY and HTTPS_PROXY set to http://127.0.0.1:7890, then restart Wonderful Launcher and retry.
Option 3: Configure a Git proxy
Deployment uses Git to clone from GitHub. If Git is not using the proxy, deployment can fail even when GitHub loads in a browser.
Global Git proxy:
git config --global http.proxy http://127.0.0.1:7890
git config --global https.proxy http://127.0.0.1:7890GitHub-only (recommended — leaves other repos unaffected):
git config --global http.https://github.com.proxy http://127.0.0.1:7890SOCKS5:
git config --global http.https://github.com.proxy socks5://127.0.0.1:7891
git config --global https.https://github.com.proxy socks5://127.0.0.1:7891Verify / remove:
git config --global --get http.proxy
git config --global --unset http.proxy
git config --global --unset https.proxyOption 4: Make sure the proxy tool is running
- Open your proxy tool and confirm it is running.
- Confirm System Proxy or Global Mode is enabled (not rule-based mode only).
- Visit https://github.com in a browser to confirm it loads.
- If the browser works but deployment still fails, the proxy is not reaching Git — see Option 2 or 3.
Option 5: Check disk space
Deploying ComfyUI needs at least 5 GB free:
Get-PSDrive -PSProvider FileSystem | Select-Object Name, @{N='Free(GB)';E={[math]::Round($_.Free/1GB,2)}}, @{N='Used(GB)';E={[math]::Round($_.Used/1GB,2)}}If space is low, free up space or change the installation directory in Wonderful Launcher settings.
Option 6: Retry the deployment
GitHub connection quality fluctuates and occasional timeouts are normal. Close the dialog and click deploy again, ideally during off-peak hours.
How this relates to other failures
This page is for the resource package download step. If the launcher gets past it but fails while cloning ComfyUI-Manager, use Deployment Failed: Installing ComfyUI-Manager. If the environment already deployed and ComfyUI itself fails to boot, use ComfyUI Startup Failed or Fix No module named errors.
Still not resolved?
Contact support through the Contact Us button in the app and include your network environment (home/corporate/school), whether you use a proxy tool (name and version), and a screenshot of the error.
Source References
Start free with Wonderful Launcher if this affects your real ComfyUI environment. It keeps launcher-native repair, task logs, and runtime checks in one place; credits are only for image generation and metered tools.
Download Wonderful LauncherSee credit packagesDid this fix your issue?
Your answer helps prioritize verified ComfyUI repairs.