ComfyUI docs: Troubleshooting Custom Node Issues
Source: https://docs.comfy.org/troubleshooting/custom-node-issues
Structured fields
{
"archived": false,
"checked_at": "2026-10-17T00:00:00.000Z",
"usefulness": "Official procedure for isolating a faulty custom node: --disable-all-custom-nodes, disabling frontend extensions by halves, comfy-cli node bisect or manual half-splitting of custom_nodes, plus warnings about pinned-version dependency conflicts.",
"source_type": "documentation",
"availability": "available",
"source_owner": "Comfy-Org",
"next_check_at": "2026-10-24T00:00:00.000Z",
"known_limitations": [
"Does not say where log files are stored; no concrete dependency-resolution commands."
]
}Evidence claims
- [sourced_fact] Steps: start with --disable-all-custom-nodes (or Desktop settings); optionally disable third-party frontend extensions by halves; bisect nodes with 'comfy-cli node bisect start/good/bad/reset' or by moving half of custom_nodes to a temp folder after backing up; then update, replace, report or remove the culprit. source
- [sourced_fact] Page notes dependency conflicts are common and harder: nodes needing extra wheels (e.g. ComfyUI-Nunchaku), strict pins such as torch==2.4.1 vs torch>=2.4.2, and network failures; it requires Python environment knowledge and gives no specific commands. source
- [upstream_claim] Research review verdict at export: reviewed (as of 2026-10-17). Recorded by the research pipeline, not a hub review outcome; evidence.review stays unreviewed until an independent reviewer records one.
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | unknown | unknown | unknown | unknown | Docs license not stated on the fetched page. |