ComfyUI: understand, install, troubleshoot

Troubleshooting ComfyUI: find the layer that breaks before touching the installation

A ComfyUI error comes from a specific layer: the software, an extension, Python, a dependency, a model, the GPU, memory or the workflow. How to find it in the console, and what not to do.

Troubleshooting ComfyUI starts with identifying the layer at fault: ComfyUI itself, an extension, Python, a dependency, a model, the GPU, VRAM or the workflow. The message shown in the interface is not always the real cause; the launch console shows the loaded extensions, the missing dependencies, the Python errors, the models that cannot be found and the CUDA problems. At Axiris, we understand the error before changing the installation: after an update, custom nodes are the first suspects, and a healthy installation is not reinstalled.

Understand the error before changing the installation

A ComfyUI error can come from several different layers, and the message visible in the interface is not always the real cause.

At Axiris, we first look for the family the error belongs to:

ComfyUI → extension → Python → dependency → model → GPU → VRAM → workflow

This distinction avoids changing a healthy installation for a failure that is not in it. You do not reinstall a machine because a model is in the wrong folder.

Read the console

The launch console is the most important source of information: before the interface, before the forums.

It shows:

  • the extensions that loaded, and those that failed;
  • the missing dependencies;
  • the Python errors, with the line where they occur;
  • the models that cannot be found;
  • the CUDA problems and the state of the GPU;
  • memory usage;
  • the origin of a hard stop.

Reading the whole console, from start-up, is the single move that solves the most failures. The error shown on screen is often the last of a series; the first one is the one that counts.

Extensions first

When a problem appears after an installation or an update, the custom nodes are the first things to check.

ComfyUI lets you disable them to find out whether the failure comes from the core software or from an extension; you then re-enable them one by one until you find the culprit. The Manager helps with this operation, but it is the console that tells you what happened.

The question that saves time

When a chain that used to work starts breaking, the useful question is not "what changed?", which is often impossible to find, but "what am I doing today that I had not done for a long time?": another image format, a model you had not reloaded, an extension whose node you had not opened for weeks. A dormant failure waits for a rare move.

What we do not do

We do not update everything just to see. We do not replace one extension with another to silence the error. We do not reinstall ComfyUI before reading the console. Each of these moves can make the symptom disappear while hiding the cause, and the cause comes back.

Official references: Troubleshooting guide · Custom node troubleshooting.

Ask the ComfyUI AI

You can pass an error or a console excerpt, or describe your installation, to the Synnexia ComfyUI AI. Its role is to help find the cause, not to suggest a random series of commands.

When the installation is no longer sustainable

Sometimes an installation has lived too long: piled-up extensions, versions nobody can trace any more, a failure every week. Axiris rebuilds it with you, keeping your models and your workflows, or delivers it ready to use: a machine in Switzerland, rented by the hour, with ComfyUI and Nova installed, maintained over time if you wish (set-up and coaching).

Contact request: a first conversation, free and with no commitment. Every practice is different; it is by listening to you that we propose what suits you.