ComfyUI Failed to Get Custom Node List? Fix It Fast

So, you opened ComfyUI. You were ready to build something epic. Maybe a new workflow. Maybe a wild AI art experiment. But then… boom. “Failed to get custom node list.” Ugh.

Don’t panic. This error looks scary. It sounds technical. But most of the time, it’s surprisingly easy to fix. You just need to know where to look.

TL;DR: If ComfyUI failed to get the custom node list, it’s usually caused by internet issues, Git problems, firewall blocks, or broken node installs. First, check your internet and restart ComfyUI. Then update Git and your custom nodes. If that doesn’t work, reinstall the nodes or check your firewall settings. Most fixes take less than 10 minutes.

What Does “Failed to Get Custom Node List” Even Mean?

ComfyUI pulls custom nodes from online sources. Usually GitHub. When it says it “failed to get custom node list,” it simply means this:

• It tried to fetch a list of available custom nodes.
• It couldn’t reach the server.
• Or something blocked the request.

That’s it.

It’s not your GPU exploding. It’s not your AI model crying. It’s usually just a connection or configuration issue.

Let’s fix it step by step.

Step 1: Check Your Internet Connection

This sounds obvious. But seriously. Check it first.

Can you open GitHub in your browser?

If not, that’s your problem.

ComfyUI needs access to the internet to fetch the custom node list. If your WiFi is down or unstable, it won’t work.

Quick fixes:

• Restart your router.
• Switch from WiFi to wired connection.
• Disable VPN temporarily.
• Try a different network.

If GitHub loads fine in your browser, move to the next step.

Step 2: Restart ComfyUI (Yes, Really)

Sometimes, the connection times out.

Sometimes, an update glitches.

Close ComfyUI completely. Not just the browser tab. Close the terminal window too.

Then launch it again.

This fixes more issues than people like to admit.

Image not found in postmeta

Step 3: Make Sure Git Is Installed and Updated

ComfyUI relies heavily on Git.

If Git is missing or outdated, fetching custom nodes may fail.

To check if Git is installed:

• Open Command Prompt (Windows) or Terminal (Mac/Linux).
• Type: git –version
• Press Enter.

If you see a version number, you’re good.

If you see an error, install Git from the official source.

If Git is installed but old, update it. Old Git versions sometimes struggle with modern GitHub connections.

Pro tip: After updating Git, restart your computer. It helps reset path variables.

Step 4: Check Your Firewall or Antivirus

This one surprises people.

Your firewall or antivirus might block Python or Git from accessing the internet.

ComfyUI runs locally. But it needs outbound access to fetch node lists.

Here’s what to do:

• Temporarily disable antivirus.
• Allow Python through your firewall.
• Add Git as a trusted app.
• Try again.

If it suddenly works, you found the culprit.

Step 5: Update ComfyUI

If your ComfyUI version is outdated, it might not communicate properly with node repositories.

Go to your ComfyUI folder.

Open a terminal inside it.

Run:

git pull

This updates ComfyUI to the latest version.

After updating, restart it again.

Try loading the custom node list.

Step 6: Manually Check the Custom Nodes Folder

Sometimes, the issue is caused by a broken custom node.

Navigate to:

ComfyUI/custom_nodes/

Look for:

• Half-installed folders
• Empty directories
• Duplicate node names
• Nodes with strange characters in the name

If you recently installed a new node and the error started after that… well, mystery solved.

Fix:

• Delete the problematic node folder.
• Restart ComfyUI.

If the error disappears, that node was broken.

Step 7: Reinstall ComfyUI Manager (If You Use It)

Many users rely on ComfyUI Manager to install custom nodes.

If Manager itself is broken, it can’t fetch the node list.

To fix it:

• Delete the Manager folder from custom_nodes.
• Re-clone it from GitHub.
• Restart ComfyUI.

This refreshes all Manager-related functionality.

Step 8: DNS Issues? Try This

Sometimes your DNS provider blocks or struggles with GitHub.

You can switch to a public DNS like:

• Google DNS: 8.8.8.8
• Cloudflare DNS: 1.1.1.1

This can instantly fix connection problems.

If you’ve never changed DNS before, search for a guide for your operating system. It takes five minutes.

Quick Comparison: Common Causes and Fixes

Problem	Symptoms	Fix	Difficulty
No Internet	GitHub won’t load	Restart router or switch network	Easy
Outdated Git	Git errors in terminal	Update Git	Easy
Firewall Block	Connection refused errors	Whitelist Python and Git	Medium
Broken Custom Node	Error after installing node	Delete problematic folder	Easy
Old ComfyUI Version	Fetch errors persist	Run git pull update	Easy
DNS Problems	Slow or unstable fetch	Switch to Google or Cloudflare DNS	Medium

Advanced: Check the Terminal Logs

If none of the simple fixes work, read the logs.

Yes. I know. Logs feel intimidating.

But you’re just looking for keywords like:

• Connection refused
• Timeout
• SSL error
• Permission denied

Copy that error line.

Paste it into a search engine.

You’ll often find someone else who had the exact same issue.

When All Else Fails: Clean Reinstall

If your setup has become messy, sometimes a clean reinstall is faster than endless debugging.

Here’s the simple way:

1. Backup your workflows.
2. Backup your models.
3. Delete the ComfyUI folder.
4. Fresh clone from GitHub.
5. Reinstall custom nodes one by one.

Install nodes slowly. Test after each one.

This way, if something breaks, you immediately know the cause.

Why This Error Is Actually a Good Sign

Weirdly enough, this error means your system is mostly working.

ComfyUI is running.

Python is running.

Your environment is mostly intact.

The problem is usually just communication with an external source.

And that’s fixable.

Prevent This From Happening Again

Here are some smart habits:

• Keep Git updated.
• Update ComfyUI regularly.
• Avoid installing random untested nodes.
• Install nodes one at a time.
• Restart after major updates.

Small habits. Big difference.

Final Thoughts

The “Failed to get custom node list” error feels dramatic. But it’s usually not.

Most fixes take less than ten minutes.

Start simple. Check internet. Restart. Update Git. Check firewall.

Only go deeper if needed.

ComfyUI is powerful. Custom nodes make it even better. And once this error is gone, you’re back to building, experimenting, and creating amazing AI workflows.

You’ve got this.