Deployment Failed: Installing ComfyUI-Manager
How to fix deployment failures at the ComfyUI-Manager installation step, especially on Windows networks where GitHub clone, proxy, SSL, or path issues block first-run setup.
Start with Wonderful Launcher if this issue touches your real ComfyUI environment. Use the docs to understand the fix, and use the app to inspect the machine you already have.
Download Wonderful LauncherIf your launcher stops at Installing ComfyUI-Manager, this is usually not a random generic install failure. It is usually one of a small number of repeatable first-run deployment problems:
- GitHub clone cannot reach
github.com - Git is available, but proxy settings are not passed through
- SSL inspection or antivirus breaks Git HTTPS
- Windows path length blocks the clone
- Git is missing or too old
This matters because the fix is different from a Python-package repair. ComfyUI-Manager is cloned through Git before the managed environment reaches a stable plugin-management state.
Symptoms
During the first ComfyUI environment deployment, the progress stalls at the "Installing ComfyUI-Manager" step and then reports a deployment failure.
Cause
ComfyUI-Manager is the plugin manager for ComfyUI (repository: https://github.com/Comfy-Org/ComfyUI-Manager). Wonderful Launcher uses git clone to download it into the custom_nodes/ directory during deployment. The clone can fail for several reasons:
- Cannot reach GitHub: Direct connections to GitHub may be unstable or blocked in certain regions
- Proxy not passed to Git: A system proxy (Clash, V2Ray, etc.) is running, but Git is not configured to use it
- SSL certificate error: Corporate networks, antivirus software, or firewalls intercept HTTPS traffic, causing Git to report
SSL certificate problem - Path too long: Windows has a default path length limit of 260 characters; deeply nested directories can trigger a
Filename too longerror - Git not installed or outdated: Git is missing from the system or the version is below 2.20
What this failure blocks
When this step fails, the first deployment may stop before the managed environment is fully ready. Users often describe that as "ComfyUI startup failed," but the more accurate diagnosis is:
deployment failed before plugin-management setup completed
That means it is usually better to solve the Git clone path first, then retry deployment, instead of immediately repairing Python packages.
Severity
High -- blocks the first deployment. ComfyUI itself can still run, but without plugin management features.
Solutions
Fastest triage order
If you want the shortest path, check the failure in this order:
- Run
git --version - Retry the clone manually in the target
custom_nodesfolder - If it hangs or cannot connect, configure proxy for Git
- If it errors on certificates, switch Git to
schannel - If it errors on path length, shorten the install path and enable long paths
That sequence usually tells you which bucket the failure belongs to within a few minutes.
Option 1: Configure a proxy for Git (recommended for users in China)
If you use a proxy tool such as Clash or V2Ray, you need to configure Git to route through the same proxy. Open Command Prompt or PowerShell and run:
HTTP proxy (Clash default port 7890):
git config --global http.proxy http://127.0.0.1:7890
git config --global https.proxy http://127.0.0.1:7890SOCKS5 proxy (some tools use a SOCKS5 port):
git config --global http.proxy socks5://127.0.0.1:7891
git config --global https.proxy socks5://127.0.0.1:7891Apply only to GitHub (to avoid affecting other repositories):
git config --global http.https://github.com.proxy http://127.0.0.1:7890
git config --global https.https://github.com.proxy http://127.0.0.1:7890After configuring, retry the deployment in Wonderful Launcher.
To remove the proxy configuration:
git config --global --unset http.proxy
git config --global --unset https.proxyOption 2: Fix SSL certificate errors
If the error message contains SSL certificate problem, a corporate network, antivirus software, or firewall may be intercepting the HTTPS connection.
Recommended -- use the Windows certificate store:
git config --global http.sslBackend schannelThis makes Git trust the same certificates as your browser, which usually resolves SSL issues in corporate network environments.
Temporary workaround -- disable SSL verification (use only on trusted networks):
git config --global http.sslVerify falseBe sure to re-enable it once the issue is resolved:
git config --global http.sslVerify trueUpdate Git:
Older versions of Git may ship with an expired CA certificate bundle. Download the latest version from https://git-scm.com/.
Option 3: Fix path-too-long errors
If the error message contains Filename too long, you need to enable long path support on Windows.
Enable Git long paths:
Open Command Prompt as Administrator and run:
git config --system core.longpaths trueEnable Windows long paths (optional, requires restart):
Open PowerShell as Administrator and run:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -ForceYou will need to sign out or restart your computer after making this change.
Additionally, consider installing ComfyUI to a shorter path (e.g., D:\ComfyUI) to avoid deeply nested directories.
Option 4: Install ComfyUI-Manager manually
If none of the above methods work, you can skip the automatic installation and do it manually.
-
Find your ComfyUI installation path in Wonderful Launcher (shown on the Environments page). The examples below assume
D:\ComfyUI. -
Open Command Prompt or PowerShell and run:
cd D:\ComfyUI\custom_nodes
git clone https://github.com/Comfy-Org/ComfyUI-Manager.gitIf a direct connection fails, specify the proxy inline:
git clone -c http.proxy=http://127.0.0.1:7890 https://github.com/Comfy-Org/ComfyUI-Manager.git- Verify the installation:
dir D:\ComfyUI\custom_nodes\ComfyUI-ManagerYou should see files such as __init__.py and a js directory. If the directory exists and is not empty, the installation was successful.
- Restart ComfyUI in Wonderful Launcher. The Manager will load automatically.
Option 5: Verify that Git is available
Confirm that Git is installed and accessible from the command line:
git --versionIf the command is not found, download and install Git for Windows from https://git-scm.com/. During installation, make sure the "Add to PATH" option is checked.
How this page relates to other startup errors
This page is for the deployment step where the launcher tries to clone ComfyUI-Manager.
If the environment already deployed and now ComfyUI itself fails to boot, use:
Still not resolved?
If the issue persists after trying all of the above, contact support through the "Contact Us" button in the app and include the following information:
- A full screenshot of the error message
- The output of
git clone https://github.com/Comfy-Org/ComfyUI-Manager.git - The output of
git config --global --list
Source References
Start with Wonderful Launcher if this issue touches your real ComfyUI environment. Use the docs to understand the fix, and use the app to inspect the machine you already have.
Download Wonderful LauncherStart with Wonderful Launcher if this issue touches your real ComfyUI environment. Use the docs to understand the fix, and use the app to inspect the machine you already have.
Download Wonderful LauncherDid this fix your issue?
Your answer helps prioritize verified ComfyUI repairs.
Manager Node List Error
Fix ComfyUI Manager failed to get custom node list by testing GitHub/raw registry access, Manager cache, proxy/firewall settings, and plugin import errors.
Safetensors Folder
Find the right ComfyUI folder for any .safetensors file: checkpoints, LoRA, VAE, ControlNet, Flux diffusion models, text encoders, and upscalers.