When ComfyUI fails to retrieve the custom node list, it can disrupt your workflow immediately—especially if you rely on community extensions for advanced pipelines, automation, or enhanced image generation. This issue is more common than many users realize and is typically linked to configuration errors, network restrictions, repository problems, or version conflicts. While the error message may appear vague, the underlying causes are usually straightforward and fixable. With a systematic approach, you can restore full functionality quickly and prevent future interruptions.
TLDR: If ComfyUI cannot fetch the custom node list, the issue is usually caused by a network blockage, outdated ComfyUI Manager, GitHub access problems, incorrect installation paths, or firewall restrictions. Start by updating ComfyUI and the Manager, verify your internet access to GitHub, and check your Python environment. Reinstalling ComfyUI Manager and confirming your custom_nodes directory structure often resolves the issue within minutes. Follow the step-by-step troubleshooting process below for a fast and reliable fix.
Why ComfyUI Fails to Get the Custom Node List
When you attempt to load or refresh the custom node list in ComfyUI Manager, it typically sends a request to retrieve repository data from an online source, usually hosted on GitHub. If this request fails, ComfyUI cannot populate the list of available nodes.
The most common reasons include:
- Network connectivity issues
- Firewall or antivirus blocking requests
- Outdated ComfyUI or ComfyUI Manager version
- Corrupted installation files
- GitHub rate limits or API access restrictions
- Incorrect Python environment configuration
Understanding which of these applies to your situation is the key to resolving the issue efficiently.
Step 1: Confirm Your Internet and GitHub Access
The first and simplest check is network access. Even if your browser appears to work normally, ComfyUI may still be blocked from accessing external repositories.
Do the following:
- Open your browser and navigate to https://github.com.
- Verify that GitHub loads without restriction.
- If using a VPN, temporarily disable it and test again.
- If on a corporate or school network, check if outbound GitHub traffic is restricted.
In restricted environments, outbound HTTPS requests to GitHub may be filtered or logged. If that is the case, using a secure home connection or configuring proxy settings inside your environment may resolve the issue.
Step 2: Update ComfyUI and ComfyUI Manager
Outdated versions are one of the most frequent causes of custom node list failures. Repository endpoints occasionally change, and older managers may not fetch data correctly.
To update ComfyUI:
cd ComfyUI git pull
To update ComfyUI Manager:
cd ComfyUI/custom_nodes/ComfyUI-Manager git pull
After updating, restart ComfyUI completely. Do not simply refresh the browser. Close the terminal session and launch it again to ensure changes apply properly.
Step 3: Verify the Custom Nodes Folder Structure
Incorrect folder structure can prevent proper detection or updating of node repositories. Your directory should look like this:
ComfyUI/ ├── custom_nodes/ │ ├── ComfyUI-Manager/ │ ├── YourOtherNodes/
Common mistakes include:
- Nesting repositories inside extra folders
- Renaming repository folders manually
- Deleting required configuration files inside ComfyUI-Manager
If you’re unsure whether your installation is intact, the fastest solution is to remove the ComfyUI-Manager folder and reinstall it:
cd ComfyUI/custom_nodes rm -rf ComfyUI-Manager git clone https://github.com/ltdrdata/ComfyUI-Manager.git
Restart ComfyUI afterward.
Step 4: Check Firewall and Antivirus Interference
Security software is a silent but frequent cause of connection failures. Firewalls may block Python or Git without clearly notifying the user.
Recommended actions:
- Temporarily disable antivirus and test again.
- Add Python and Git to your firewall whitelist.
- Ensure port 443 (HTTPS) is not blocked.
- On Windows, allow Python through Windows Defender Firewall.
If disabling security software resolves the issue, create permanent exceptions rather than keeping protection disabled.
Step 5: Confirm Proper Python Environment
ComfyUI relies heavily on your Python environment. If packages are broken or outdated, repository calls can fail.
Check your Python version:
python --version
ComfyUI typically works best with Python 3.10. Versions too old or too new may introduce compatibility issues.
Next, reinstall key dependencies:
pip install -r requirements.txt --upgrade
If your environment is heavily modified, consider creating a clean virtual environment and reinstalling ComfyUI entirely.
Step 6: Watch for GitHub API Rate Limits
GitHub limits unauthenticated API requests. If many requests are sent within a short timeframe, additional calls may fail temporarily.
Solutions include:
- Waiting 30–60 minutes before retrying
- Authenticating Git with a GitHub account
- Using a personal access token
Heavy automation setups or shared networks are more prone to hitting limits.
Step 7: Full Clean Reinstallation (Last Resort)
If none of the above resolves the issue, a clean reinstall is often faster than continued troubleshooting.
- Back up your custom_nodes folder.
- Delete the entire ComfyUI directory.
- Download a fresh copy from the official repository.
- Reinstall ComfyUI-Manager.
- Reintroduce custom nodes one by one.
This method eliminates hidden corruption, misconfiguration, and residual file conflicts.
Quick Troubleshooting Checklist
- ✔ Confirm GitHub loads in your browser
- ✔ Update ComfyUI
- ✔ Update ComfyUI Manager
- ✔ Check firewall and antivirus settings
- ✔ Verify Python version (3.10 recommended)
- ✔ Confirm correct folder structure
- ✔ Consider GitHub rate limits
Tool Comparison: Methods to Fix the Issue
| Method | Difficulty | Time Required | Effectiveness |
|---|---|---|---|
| Update ComfyUI and Manager | Easy | 5–10 minutes | High |
| Check Network and Firewall | Moderate | 10–20 minutes | High |
| Reinstall ComfyUI Manager | Easy | 5 minutes | Very High |
| Rebuild Python Environment | Moderate | 20–40 minutes | Very High |
| Full Reinstallation | Moderate | 30–60 minutes | Maximum |
How to Prevent This Problem in the Future
Prevention is more efficient than repair. Consider implementing these best practices:
- Keep ComfyUI updated weekly.
- Avoid manually modifying repository structures.
- Use a stable internet connection for updates.
- Maintain a clean Python virtual environment.
- Back up custom nodes before major changes.
Documenting your setup—Python version, installed nodes, and ComfyUI commit version—can save significant time if troubleshooting becomes necessary later.
When the Issue Is Server-Side
Occasionally, the failure originates outside your system. GitHub outages or repository changes can temporarily disrupt node list retrieval.
If everything appears correct locally:
- Check GitHub status pages.
- Verify the ComfyUI Manager repository is accessible.
- Search community forums for similar reports.
If other users report the same issue, it is likely temporary.
Final Thoughts
A failed custom node list in ComfyUI may look serious at first glance, but in most cases the solution is straightforward. The majority of issues stem from outdated components, firewall restrictions, or minor installation inconsistencies. By methodically checking connectivity, updating software, verifying structure, and ensuring a clean Python setup, you can resolve the problem quickly and prevent recurrence.
ComfyUI is a powerful, modular system. With that flexibility comes dependency on external repositories and network access. Maintaining disciplined update habits and a clean environment ensures the custom node ecosystem continues working exactly as designed—stable, accessible, and efficient.