Blank ComfyUI screen after an extension update: separate frontend and backend failures
The Python server may still be running while the canvas fails. Distinguish static assets, JavaScript extensions and an absent backend before reinstalling unrelated models.
Symptoms and scope
The Python server may still be running while the canvas fails. Distinguish static assets, JavaScript extensions and an absent backend before reinstalling unrelated models.
Error fragments for search; IDs, values and filenames may vary:
Failed to fetch dynamically imported module
TypeError
blank screen
Source-supported context
Official troubleshooting provides separate frontend-extension and backend-node isolation paths. Update instructions distinguish frontend, core and templates rather than treating them as one version. Source 1 Source 2
Cases to distinguish
1. Cache or a proxy returns incompatible frontend resources.
2. Extension JavaScript no longer matches the frontend API.
3. Backend startup, proxy routing or static-resource authorization fails.
Diagnostic sequence
The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.
Step 1. Confirm the terminal's listening address and a live backend, then inspect browser Console and Network errors.
Step 2. Preserve unsaved workflows before comparing a private window or fresh browser profile. Do not erase the only local copy of work.
Step 3. If Settings opens, disable third-party frontend extensions through its Extensions menu, restart, then restore groups gradually. If the blank screen prevents access to Settings, back up the installation and use its supported disable-all-custom-nodes procedure for a baseline comparison; restore node groups gradually to isolate the trigger. A clean baseline narrows the cause but does not identify a particular extension by itself.
Step 4. Record the first resource/script error and versions, testing an update or rollback in a copy without changing networking and dependencies simultaneously.
Completion check
The canvas, node interactions and baseline requests recover and refreshing no longer reproduces the script failure. A visible homepage is not complete extension validation.
Limitations and cautions
Disabling an extension does not undo packages it installed. Clearing browser storage can destroy unsynchronized work.
Original sources
- ComfyUI custom node troubleshooting — checked 2026-09-26.
- How to update ComfyUI — checked 2026-09-26.
English source review: 2026-09-26. The sequence follows the current official UI-access branch; no local ComfyUI run, GPU test, minimum-memory measurement or repair outcome is claimed.
Related troubleshooting and guides
Was this page helpful?
Anonymous. Only a yes/no counter is stored; no account, IP address or device details.
Sources & references
Reviewed official ComfyUI custom-node troubleshooting and update guidance on 2026-09-26, including the no-Settings fallback. The diagnostic sequence is editorial; no local ComfyUI run, GPU test or confirmed repair is claimed.
01ComfyUI custom node troubleshootingSource checked: 2026-09-2602How to update ComfyUISource checked: 2026-09-26