ComfyUI common issues

Use this page to identify and resolve common issues with ComfyUI on Olares.

Need more help?

If you are encountering an issue that is not listed here, refer to Troubleshooting flow.

How to migrate to the new ComfyUI after upgrading to Olares 1.12.6

Use this section if you upgraded to Olares 1.12.6 and already had ComfyUI Shared installed. If you are installing ComfyUI for the first time on Olares 1.12.6 or later, install ComfyUI directly from Market.

Olares 1.12.6 updates the shared app architecture. The old ComfyUI Shared app can still run after the upgrade, but it cannot receive future updates. To keep ComfyUI up to date, uninstall the old app without deleting local data, then install the new ComfyUI app from Market.

WARNING

When uninstalling the old app, do not select Also remove all local data. Selecting this option may delete your models, plugins, workflows, and input/output files.

Migration steps

1. Open Market and go to My Olares.
2. Find ComfyUI Shared, click the dropdown arrow next to its operation button, and select Uninstall.
3. In the Uninstall window, leave Also remove all local data unselected, then click Confirm.
4. In Market, search for "ComfyUI" and click Install.
5. On the app details page, check Information > Compatibility. If it shows Olares >=1.12.6-0, you are installing the new version.
6. After installation, open ComfyUI and check that your models, plugins, workflows, and input/output files are available.

What gets migrated

After the new ComfyUI is installed, data is migrated automatically as follows:

Data type	Old location	New location
ComfyUI core (plugins, workflows, etc.)	External/<your_hostname>/ai/comfyui/	/Data/comfyuisharev3/comfyui/
Models	External/<your_hostname>/ai/model/	Common/comfyui/model/
Output files	External/<your_hostname>/ai/output/comfyui/	Common/comfyui/output/
Input files	External/<your_hostname>/ai/comfyui/ComfyUI/input/	Common/comfyui/input/

WARNING

After migration, upload new models and input files to the new locations under Common/comfyui/. The new ComfyUI no longer uses External/<your_hostname>/ai/ as its active file location.

The migration runs each time ComfyUI restarts. If files are later added to the old locations, ComfyUI will move them to the new locations on the next restart and delete the originals from External/<your_hostname>/ai/. To avoid confusion, upload new files directly to the new locations.

ComfyUI cannot start

ComfyUI fails to start, stops unexpectedly, or behaves abnormally.

This is usually caused by insufficient resources or incorrect GPU allocation. To resolve this:

1. Check your system resources. If your CPU or memory usage is maxed out, stop other resource-intensive apps.
2. If system resources look fine, go to Settings > Accelerator and check your GPU mode:
   • If you are using Memory slicing, make sure ComfyUI is bound to the GPU and has enough VRAM allocated.
   • If you are using Exclusive, make sure the exclusive app is set to ComfyUI.
3. Wait a moment, then try to launch ComfyUI again.

Launcher log shows errors

Error messages in the Launcher logs do not necessarily indicate a system failure. During startup and plugin scanning, ComfyUI often logs non-fatal errors for missing optional dependencies or environment checks, even when running normally.

If ComfyUI starts successfully, most of these messages do not require action. Investigate logs only if ComfyUI fails to start, a workflow cannot run, or a plugin stops working.

ComfyUI fails to start after upgrading to v1.0.37 or later

This issue may occur after upgrading to ComfyUI v1.0.37 or later.

After the upgrade, ComfyUI app may fail to start and show an error like:

main.py: error: unrecognized arguments: --normalvram

This means a custom launch argument from a previous version is still in use, but the new version no longer supports it.

To fix this:

1. Open ComfyUI Launcher and go to Lab from the left sidebar.
2. In the Manually edit extra arguments field, remove --normalvram manually and click SAVE MANUAL ARGS. Alternatively, click RESTORE DEFAULT to reset to the default launch arguments.
3. Verify that Current full launch command at the top no longer contains --normalvram.
4. Go back to Home in ComfyUI Launcher, then click Start to launch ComfyUI.

Models cannot be downloaded directly to Olares

Some models require login, access approval, a token, or manual confirmation before they can be downloaded. These models cannot be downloaded directly to Olares through ComfyUI Launcher or Server Download.

To solve it, find the download link using one of the methods below. Then download the model manually and upload it to the correct folder in Olares Files.

Method 1: Check the template notes or Model Links section

Some official templates include notes or a Model Links section that lists:

• The required model file
• The download URL
• The expected storage location

If available, copy the download URL or open the model page directly.

Method 2: Use a browser helper extension

If the template shows a missing-model dialog and does not expose the full URL, use a browser helper extension like WAN Download URL Helper:

1. Open the missing-model dialog in ComfyUI.
2. Hover over a download icon.
3. Right-click the icon and choose Show download URL.
4. Copy the URL, then use it in your downloader or save it for manual download.

Method 3: Inspect the page in browser developer tools

If the URL is not shown in the template notes or dialog, inspect the page in your browser developer tools and look for network requests triggered by the template or missing-model dialog.

CPU temperature rises unusually high on Olares One

When a workflow requires more VRAM than your graphics card has, the system places heavy load on a single CPU core to swap data, driving the temperature high.

The long-term fix is to reduce the VRAM footprint of your workflow (for example, lower resolution, use a smaller model, or enable model offloading). As a temporary workaround, limit the maximum CPU frequency while the workload is running.

Olares OS 1.12.6 or later

Olares One ships with a CPU whose default maximum frequency is 5.4 GHz. Use the Limit CPU frequency switch to lower it to 5.0 GHz during the workload, then turn the switch off when the workload completes.

1. Open Settings.
2. Select your avatar in the top-left corner to open My Olares.
3. Under My hardware, turn on Limit CPU frequency.
4. Run your task in ComfyUI.
5. After the workload completes, turn off Limit CPU frequency.

For more details, see Limit CPU frequency.

Olares OS 1.12.5 or earlier

If your device is running Olares OS 1.12.5 or earlier, use terminal commands to lower the maximum CPU frequency during the workload, then restore it afterward.

1. Open the Control Hub app.

2. In the left sidebar, under Terminal, click Olares.

   

3. Run the following command to lower the maximum CPU frequency to 5.0 GHz:

   echo 5000000 | sudo tee /sys/devices/system/cpu/cpufreq/policy*/scaling_max_freq

   On other devices, adjust the target value based on your CPU's maximum frequency. Run cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq to check it first.

4. Run your task in ComfyUI.

5. After the workload completes, run the following command to restore the default maximum CPU frequency of 5.4 GHz:

   echo 5400000 | sudo tee /sys/devices/system/cpu/cpufreq/policy*/scaling_max_freq