ComfyUI Failed to Get Custom Node List or ComfyRegistry Fix
Fix ComfyUI Manager failed to get custom node list, failed to find the following ComfyRegistry list, stale cache, proxy/firewall blocks, and registry network failures.
failed to get custom node list (and related messages like cannot connect to ComfyRegistry, failed to fetch versions from ComfyRegistry, or failed to find the following ComfyRegistry list. the cache may be outdated, or the nodes may have been removed from ComfyRegistry) means ComfyUI Manager could not load or trust the registry data it uses to search, install, update, or match custom nodes. This is usually a Manager fetch, cache, or network problem — not proof that your whole install is broken.
If the UI is stuck on Reconnecting... or says failed to fetch server logs, use those dedicated guides instead: Reconnecting, Failed to Fetch Server Logs.
If the visible browser message is only Failed to fetch, use ComfyUI "Failed to Fetch" first to confirm whether the failed request belongs to Manager, server logs, WebSocket reconnecting, or workflow draft saving.
Exact error logs
failed to get custom node list
cannot connect to comfyregistry
failed to fetch versions from comfyregistry
error connecting to the comfy node registry.
[error] [comfyui-manager] an invalid channel was used: https://raw.githubusercontent.com/ltdrdata/comfyui-manager/main
failed to find the following comfyregistry list. the cache may be outdated, or the nodes may have been removed from comfyregistry.Do not install Python packages from words inside these errors. A missing string here is usually a registry package id, not a pip package.
Triage
| What you see | Most likely cause | First check |
|---|---|---|
| Error only when opening Manager or installing missing nodes | Manager cannot fetch its registry | Test GitHub and raw GitHub access |
cannot connect to ComfyRegistry | Registry API, raw GitHub, proxy, DNS, or firewall blocking the list | Test browser access and another network |
failed to fetch versions from ComfyRegistry | Reached the feature but could not load version metadata | Check network/proxy and retry before reinstalling |
the cache may be outdated, or the nodes may have been removed | Cached data mismatch or delisted node | Clear only Manager cache after confirming network |
| Existing workflows still run | List-fetch problem, not a full failure | Do not reinstall yet |
IMPORT FAILED appears in startup logs | Installed node or dependency broke import | Fix the import error first |
| Works on another network | Proxy, firewall, DNS, or regional block | Test hotspot, VPN, or proxy settings |
If it blocks missing-node repair
When this appears during Install Missing Custom Nodes, separate three states — they need different fixes:
| State | What is true | What to do |
|---|---|---|
| Manager cannot fetch its list | Registry list or raw GitHub data cannot load | Fix Manager registry/network/cache first |
| Manager found the node pack but clone failed | Mapping may be correct, but the download failed | Fix Git, PATH, proxy, GitHub, or repo access |
| Plugin installed but nodes are still red | The folder exists, but the plugin did not register | Check IMPORT FAILED and repair the plugin dependency |
Step 1: Check whether ComfyUI still runs
Does the default workflow load, queue an image, and show installed nodes? If ComfyUI runs and only Manager fails to fetch the list, treat this as a Manager/network/cache problem. If ComfyUI fails at startup, freezes, reconnects, or shows import errors, start with Startup Failed or Plugin Import Failed.
Step 2: Check GitHub and registry access
On the same machine, test the Manager repo:
https://github.com/Comfy-Org/ComfyUI-ManagerThen the raw list path:
https://raw.githubusercontent.com/Comfy-Org/ComfyUI-Manager/main/custom-node-list.jsonIf the page opens but the raw URL fails, your network, DNS, proxy, antivirus, or firewall may be blocking raw GitHub assets. Try another browser, another network or mobile hotspot, disabling web filtering, or checking VPN/proxy settings.
Step 3: Read the Manager log line
Look at the terminal output around the error for clues such as FETCH DATA from:, custom-node-list.json, ConnectionError, SSLError, or TimeoutError. A network/SSL/proxy error means fix connectivity first. Local cache paths mean Manager is trying to read cached files. IMPORT FAILED means the list error may be secondary.
Step 4: Separate missing nodes from missing registry entries
Manager can find missing nodes in a workflow only when it can access its list, and only for nodes that are registered. If one workflow fails, inspect the red node names and search the author's page or README. If many workflows fail, your Manager list or network access is the more likely problem. For safer manual installs, use Install ComfyUI Custom Nodes Without Breaking Your Environment.
Step 5: Clear Manager cache only after checking network
If GitHub and raw GitHub work but Manager still cannot load the list, cache may be stale. Cache locations vary by install and Manager version, often near:
ComfyUI/user/default/ComfyUI-Manager/cache/
ComfyUI/user/__manager__/cache/Before deleting anything:
- Stop ComfyUI.
- Copy the cache folder somewhere safe.
- Delete only Manager cache files, not workflows, models, or custom node folders.
- Restart ComfyUI and open Manager again.
Clearing cache will not help if the same network cannot reach the registry.
Step 6: Repair import failures before installing more nodes
If startup logs already show IMPORT FAILED, ModuleNotFoundError, or ImportError, fix the first import failure, restart, confirm Manager opens, then retry missing-node installation. If a recent install broke the environment, use Installed Custom Nodes and Broke ComfyUI.
Step 7: Use the correct Python for a manual Manager repair
Use the same Python that launches ComfyUI. For Windows portable, avoid system Python:
python_embeded\python.exe -m pip install -r ComfyUI\custom_nodes\ComfyUI-Manager\requirements.txtFor a manual or venv install:
cd ComfyUI/custom_nodes/ComfyUI-Manager
pip install -r requirements.txtDo not run pip install -r requirements.txt blindly.
- Confirm which Python environment is active (
where pythonorwhich python) - Inspect
requirements.txt— check if it pins torch, numpy, or opencv versions - Install only the missing package when possible:
pip install <package-name> - Run
pip checkafter installation to verify no conflicts were introduced
When to reinstall Manager
Reinstall only after checking network access and cache. For a manual install:
cd ComfyUI/custom_nodes
git clone https://github.com/Comfy-Org/ComfyUI-Manager.gitIf a ComfyUI-Manager folder already exists, stop ComfyUI and back it up before updating or reinstalling. For ComfyUI Desktop or a managed package, use the package's own update path.
Related Manager Guides
- ComfyUI Manager: Install, Open, Update, and Troubleshoot
- How to Install ComfyUI Custom Nodes Without Breaking Your Environment
- How to Fix ComfyUI Plugin Import Failed Errors
- Installed Custom Nodes and Broke ComfyUI? Recover Without Reinstalling
- ComfyUI Reconnecting Error: Causes and Fast Fixes
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.