-
-
Notifications
You must be signed in to change notification settings - Fork 4
Troubleshooting
Check these items:
- Confirm that ComfyUI has the workflow loaded in the active graph.
- Click Force Rescan in Model Resolver.
- Check the model category and the directories configured in ComfyUI.
- Clear the frontend and backend cache from Options > Maintenance.
- Check whether the model belongs to a custom loader supported by the current adapter.
Model Resolver can only inspect model references present in the workflow data. A custom node that hides its model selection from the workflow may require an adapter update.
Open the source status row and check the provider message. Then:
- Enable the source in Options > Download Sources.
- Check the provider credential if the repository or model requires account access.
- Select the provider directly instead of Everything.
- Retry the provider when the status says
unavailableorrate_limited. - Use the local model list update when the filename should exist in the ComfyUI-Manager database.
Provider outages do not prove that a model is absent. Retry the affected source after it recovers.
Check the selected category, root folder, and available disk space. For provider-specific errors, verify the matching credential and accepted terms.
If aria2 fails:
- Use Options > Download Sources > Check aria2.
- Leave
aria2c pathempty whenaria2cis available inPATH. - Use Install aria2 to install the managed executable.
- Switch to the Python backend to test the same URL through the built-in downloader.
See Aria2 Download Backend for the full setup guide.
Wait for the download to reach completed, then refresh the local match list. Check that the file exists below the selected ComfyUI model root and that its category matches the loader. Select the completed local match and click Apply.
Enable Refresh ComfyUI models after Apply when ComfyUI does not expose a newly downloaded file until it refreshes its model catalogs.
Hash matching requires the exact local file. A different revision, an incomplete download, or a converted model produces a different SHA-256 value. Calculate the local hash from the model details view and compare the complete value with the provider result.
Export frontend and backend logs from Options > Maintenance. Include:
- ComfyUI version.
- Model Resolver version.
- Operating system.
- Provider and download backend.
- The source status or error message.
- The model category and target path, with tokens and private URLs removed.