ComfyUI Node Not Found Error Fix

Updated June 2026

The "Node Not Found" error in ComfyUI typically appears when you load a workflow that references a custom node not present or correctly installed in your ComfyUI setup. The exact message might look like this: Error: No such node type ‘SomeCustomNode’ Node ‘SomeCustomNode’ does not exist.

Understanding the “Node Not Found” Error

The "Node Not Found" error in ComfyUI typically appears when you load a workflow that references a custom node not present or correctly installed in your ComfyUI setup. The exact message might look like this:

Error: No such node type 'SomeCustomNode'

Node 'SomeCustomNode' does not exist.

This error prevents your workflow from loading or executing, halting your creative process. It happens because ComfyUI cannot locate the specific Python module or file that defines the referenced node.

Fix 1: Install or Reinstall Missing Custom Nodes

The most common cause is a missing custom node. You need to identify and install it.

1.1 Using Comfy Manager (Recommended)

Comfy Manager is the easiest way to handle custom nodes.

1. Identify the Missing Node: Look at the error message in ComfyUI or your terminal. It will usually specify the name of the missing node (e.g., ‘Efficiency Nodes’, ‘WAS Suite’).
2. Open Comfy Manager: Start ComfyUI. If Comfy Manager is installed, you’ll see a "Manager" button at the bottom of the interface. Click it.
3. Install Custom Nodes: In the Manager menu, select "Install Custom Nodes."
4. Search and Install: Use the search bar to find the custom node identified in the error message. Click "Install" next to the correct entry.
5. Restart ComfyUI: After installation, restart ComfyUI completely to ensure the new node is loaded.

1.2 Manual Installation (If Manager Not Used or Fails)

If you don’t use Comfy Manager or it fails, you can install nodes manually.

1. Find the Node’s Repository: Search online (e.g., GitHub) for the custom node you need. Most custom nodes for ComfyUI are hosted on GitHub.
2. Navigate to custom_nodes: Go to your ComfyUI installation directory. Inside, you’ll find a folder named custom_nodes. This is where all custom nodes should reside.
3. Clone or Download:
   • Using Git (recommended): Open a terminal or command prompt in the custom_nodes folder. Use the git clone command with the repository URL (e.g., git clone https://github.com/owner/repo-name.git).
   • Manual Download: Download the repository as a ZIP file from GitHub, extract it, and place the extracted folder directly into your custom_nodes directory. Ensure there’s no extra subfolder level (e.g., ComfyUI/custom_nodes/repo-name, not ComfyUI/custom_nodes/repo-name-main/repo-name).
4. Install Dependencies: Many custom nodes require additional Python libraries. Check the node’s GitHub page for installation instructions. Often, this involves navigating into the newly installed node’s folder (e.g., ComfyUI/custom_nodes/repo-name) and running pip install -r requirements.txt.
5. Restart ComfyUI: Close and reopen ComfyUI.

Fix 2: Update ComfyUI and Custom Nodes

Outdated ComfyUI or custom nodes can lead to compatibility issues, resulting in "node not found" errors.

2.1 Update ComfyUI (Recommended via Manager)

1. Open Comfy Manager: Click the "Manager" button in ComfyUI.
2. Update ComfyUI: Select "Update ComfyUI" and click the "Update" button.
3. Restart ComfyUI: Relaunch ComfyUI after the update completes.

Diagnostic checklist before you escalate

Most web-app failures can be narrowed to service status, one account session, browser data, an extension, or the network. Test those boundaries in order rather than clearing everything at once. A private window and a second network are especially useful because they change one layer without altering your account data.

1. Check the provider’s official status page before changing local settings.
2. Hard-refresh, start a new session, and test a private browser window.
3. Disable content blockers, privacy extensions, VPN, proxy, and secure DNS temporarily.
4. Compare another browser, device, and network to locate the failing boundary.
5. Record timestamps, error text, and the smallest reproducible sequence for support.

Verify the recovery across session and network boundaries

When ComfyUI Node Not Found Error starts working, repeat the original action in a fresh tab and then in the normal browser profile. Confirm that buttons, uploads, saved history, and live updates behave normally instead of only rendering the first screen. If private mode works but the regular profile fails, continue isolating cookies and extensions rather than declaring the service fixed.

Restore extensions, VPN, proxy, secure DNS, and content filtering one at a time. Reload after each change. This controlled restoration identifies the incompatible layer and prevents the common outcome where everything is disabled permanently. Finish by testing one other device or network so you know whether the recovery belongs to the account, the device, or the connection.

• The original action succeeds twice in a fresh session.
• The normal browser profile works after cleanup.
• Extensions and network controls are restored individually.
• Saved data and account history remain available.
• A second device or network confirms the result.

Keep a short note of the working configuration and the date of the test. Products, models, browser versions, limits, and safety policies change over time, so a previously successful workaround may later become obsolete. Prefer current official documentation over old forum instructions, and reverse temporary diagnostic changes once testing is complete. This gives you a reliable baseline without leaving extensions disabled, security controls weakened, or experimental settings enabled indefinitely. Recheck the baseline after major updates before assuming an older failure has returned for the same reason.

When none of the fixes work

Repeat the smallest failing action once and record the exact local time and time zone. Note the product, model or feature, account plan, browser or app version, operating system, and whether the same action works in a private window, on another device, or on another network. This evidence is much more useful than saying the tool is “still broken.”

Use the provider’s official support channel. Include a screenshot with sensitive information removed and list the steps already tested. For developer tools, add sanitized request and response details, correlation IDs, and SDK versions. Never send passwords, one-time codes, API keys, session cookies, private repository contents, or complete payment information.

FAQ

Q1: Why does this error happen even after I install a node?
It can happen if the node’s required Python dependencies weren’t installed, if ComfyUI wasn’t restarted, or if the node’s folder structure is incorrect (e.g., an extra subfolder level).

Q2: Can I run ComfyUI without custom nodes?
Yes, ComfyUI works perfectly fine with its default nodes. The "node not found" error only occurs when you load a workflow that explicitly tries to use a custom node that isn’t available.

Q3: What if Comfy Manager isn’t installed?
You can install Comfy Manager manually by following its instructions, typically involving cloning its repository into your custom_nodes folder and restarting ComfyUI. If you prefer not to use it, you’ll need to install and update custom nodes manually via Git and pip as described in Fix 1.2 and 2.3.

The solution for a "ComfyUI node not found" error almost always involves correctly installing, updating, or verifying the path of the missing custom node and its dependencies.

Bottom line: Work from the least disruptive test to the most specific one. Confirm service health, isolate session and network variables, then escalate with clean evidence instead of repeating the same failing action.