So you opened ComfyUI, ready to build something amazing… and boom. You see the dreaded message: “Failed to Get Custom Node List.” Annoying, right? Don’t worry. You’re not alone. And the good news? This error is usually easy to fix.
TLDR: If ComfyUI can’t fetch your custom node list, it’s often caused by internet issues, GitHub rate limits, outdated extensions, or folder misplacements. Most fixes take less than 10 minutes. Restarting ComfyUI, updating nodes, or checking your file paths usually solves it. Follow the eight quick fixes below and you should be back up and running fast.
Why This Happens in the First Place
Before we fix it, let’s make it simple.
ComfyUI pulls custom node lists from online sources. Usually GitHub. If something blocks that connection, the list won’t load. That’s it.
Common causes include:
- Internet issues
- GitHub API rate limits
- Broken or outdated custom nodes
- Wrong folder structure
- Firewall or antivirus blocks
- Old ComfyUI version
Now let’s fix it.
1. Check Your Internet Connection
Yes. Start simple.
If ComfyUI can’t reach GitHub, it can’t fetch the custom node list.
Open your browser and try visiting GitHub. If it loads slowly or not at all, that’s your problem.
Quick Fix:
- Restart your router
- Switch networks if possible
- Turn off VPN temporarily
VPNs sometimes trigger rate limits. Turning it off often fixes the issue instantly.
2. You Hit the GitHub API Rate Limit
GitHub limits how many requests you can make per hour.
If you refresh a lot. Or reinstall nodes often. You may hit that limit.
When that happens, ComfyUI can’t fetch data.
How to Fix It:
- Wait one hour and try again
- Add a GitHub personal access token
Adding a token increases your rate limit dramatically.
Simple steps:
- Go to GitHub → Settings → Developer Settings
- Create a personal access token
- Add it to ComfyUI Manager settings
After that, restart ComfyUI.
3. Update ComfyUI
Running an older version?
That may be the issue.
Custom node lists sometimes change format. Older versions of ComfyUI may not understand the new structure.
Quick Fix:
Open your ComfyUI folder and run:
git pullOr update using the ComfyUI Manager if you have it installed.
Restart after updating.
Still broken? Keep going.
4. Update or Reinstall the ComfyUI Manager
The error often comes from the Manager extension, not ComfyUI itself.
If the Manager is outdated, it may fail to pull the custom node list.
Fix:
- Go to your custom_nodes folder
- Delete the ComfyUI-Manager folder
- Reinstall it from its official repository
Then restart ComfyUI.
Simple. Clean. Effective.
Image not found in postmeta5. Check Your Folder Structure
This one trips people up all the time.
Your custom nodes must be inside:
ComfyUI/custom_nodes/Not:
- Inside another random folder
- Nested twice by accident
- Zipped
Wrong example:
ComfyUI/custom_nodes/custom_nodes/some_nodeCorrect example:
ComfyUI/custom_nodes/some_nodeIf you accidentally unzipped incorrectly, fix it.
Remove extra layers.
Restart ComfyUI.
6. Disable Firewall or Antivirus (Temporarily)
Some security software blocks Python requests to GitHub.
ComfyUI uses Python to fetch node lists.
If your firewall blocks that request, you’ll see the error.
Quick Test:
- Temporarily disable antivirus
- Allow Python through firewall
- Try again
If it works, add an exception instead of leaving protection off.
Security matters. But so do nodes.
7. Delete Corrupted Node Installations
One broken custom node can mess up the whole list.
If a recently installed node caused the issue, remove it.
Steps:
- Open custom_nodes
- Delete the newest or suspicious folder
- Restart ComfyUI
If the error disappears, you found the culprit.
You can try reinstalling that node cleanly.
8. Do a Clean ComfyUI Reinstall (Last Resort)
If nothing works, go nuclear.
Don’t worry. It’s not hard.
Steps:
- Backup your models folder
- Backup your custom_nodes folder
- Delete ComfyUI entirely
- Download a fresh copy
- Re-add models and nodes one by one
Add nodes slowly. Test after each batch.
This helps you detect which one breaks things.
Quick Comparison of Fix Options
| Fix | Difficulty | Time Needed | Best For |
|---|---|---|---|
| Check Internet | Very Easy | 2 minutes | Connection issues |
| Add GitHub Token | Easy | 5 minutes | Rate limit errors |
| Update ComfyUI | Easy | 3 minutes | Old versions |
| Reinstall Manager | Easy | 5 minutes | Manager bugs |
| Fix Folder Structure | Medium | 5 minutes | Misplaced nodes |
| Adjust Firewall | Medium | 5–10 minutes | Blocked connections |
| Remove Broken Node | Medium | 10 minutes | Recent installations |
| Clean Reinstall | Harder | 30+ minutes | Major corruption |
Pro Tips to Avoid This Error in the Future
Let’s prevent this from happening again.
- Don’t install random nodes all at once. Test each one.
- Keep ComfyUI updated. Small updates prevent big problems.
- Use a GitHub token. Avoid rate limits forever.
- Organize your custom_nodes folder. Keep it clean.
- Backup weekly. Seriously. It saves headaches.
Think of ComfyUI like a workshop.
Messy workshop? Hard to work.
Clean workshop? Smooth building.
Still Not Working?
If you tried all eight fixes and nothing worked, check:
- The console log for detailed Python errors
- Whether GitHub itself is down
- Community forums for similar reports
Copy the full error message.
Search it exactly as written.
Chances are, someone already solved it.
Final Thoughts
The “Failed to Get Custom Node List” error sounds scary.
But it usually isn’t.
Most of the time, it’s just:
A connection issue.
A rate limit.
An outdated extension.
Or a misplaced folder.
Nothing dramatic.
Follow the fixes step by step. Don’t panic. Start simple. Move to advanced only if needed.
Soon enough, your custom nodes will be back.
And you’ll be building workflows like a pro again.
Now go fix it. 🚀