[GH-ISSUE #1950] Could you just DISABLE THE MANDATORY FETCH ComfyRegistry Data? #820

Open
opened 2026-10-27 21:22:37 +00:00 by bsakaguchi · 7 comments
Owner

Originally created by @allroundHim on GitHub (Jun 25, 2025).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1950

V3.31.9 manager in comfy portable

I set COMMANDLINE_ARGS=--dont-fetch-updates in comfy launch nvidia gpu.bat.
It works only when starting the webui, after the webui is loaded in browser, the fetch process start again!!!!

Everytime I launch comfy UI it takes a f******** long time to fetch comfyRegistry Data, it is ridiculous that this time consuming event should not be unconditioned! IT WOULD TAKE MORE THAN 2 MINUTES TO fetch all 90 registry

I tried this:
To disable FETCH DATA, you can change network_mode to private or offline. https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config

This is from https://github.com/Comfy-Org/ComfyUI-Manager/issues/1629

However, in my custom node directory this is no "ComfyUI-Manager" directory, there is only a folder named "ComfyUI-Manager-main"
while the cmd treat is like ComfyUI-Manager folder, there is NO config.ini in this folder.
I even manually creat a config.ini and add network_mode = private, but it does not work.
It still FETCH those registry data.
IT'S JUST HORRIBLE WE DON'T HAVE SO MUCH TIME IN LIFE

Originally created by @allroundHim on GitHub (Jun 25, 2025). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1950 V3.31.9 manager in comfy portable I set COMMANDLINE_ARGS=--dont-fetch-updates in comfy launch nvidia gpu.bat. It works only when starting the webui, after the webui is loaded in browser, the fetch process start again!!!! Everytime I launch comfy UI it takes a f******** long time to fetch comfyRegistry Data, it is ridiculous that this time consuming event should not be unconditioned! IT WOULD TAKE MORE THAN 2 MINUTES TO fetch all 90 registry I tried this: `To disable FETCH DATA, you can change network_mode to private or offline. https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config` This is from https://github.com/Comfy-Org/ComfyUI-Manager/issues/1629 However, in my custom node directory this is no "ComfyUI-Manager" directory, there is only a folder named "ComfyUI-Manager-main" while the cmd treat is like ComfyUI-Manager folder, there is NO config.ini in this folder. I even manually creat a config.ini and add network_mode = private, but it does not work. It still FETCH those registry data. IT'S JUST HORRIBLE WE DON'T HAVE SO MUCH TIME IN LIFE
Author
Owner

@koticR commented on GitHub (Jun 28, 2025):

there is NO config.ini in this folder.
I even manually creat a config.ini and add network_mode = private, but it does not work.

The 'config.ini' is not located in the 'ComfyUI-Manager' folder inside your 'custom_nodes' folder. It is located in your root 'ComfyUI' folder under 'user/default/ComfyUI-Manager/'

Everytime I launch comfy UI it takes a f******** long time to fetch comfyRegistry Data, it is ridiculous that this time consuming event should not be unconditioned! IT WOULD TAKE MORE THAN 2 MINUTES TO fetch all 90 registry

You don't have to wait for this process to finish before starting to generate. The moment you see the 'To see the GUI go to: http...' you are good to go.

<!-- gh-comment-id:3014966339 --> @koticR commented on GitHub (Jun 28, 2025): > there is NO config.ini in this folder. I even manually creat a config.ini and add network_mode = private, but it does not work. The '_config.ini_' is not located in the '_ComfyUI-Manager_' folder inside your '_custom_nodes_' folder. It is located in your root '_ComfyUI_' folder under '_user/default/ComfyUI-Manager/_' > Everytime I launch comfy UI it takes a f******** long time to fetch comfyRegistry Data, it is ridiculous that this time consuming event should not be unconditioned! IT WOULD TAKE MORE THAN 2 MINUTES TO fetch all 90 registry You don't have to wait for this process to finish before starting to generate. The moment you see the '_To see the GUI go to: http..._' you are good to go.
Author
Owner

@ltdrdata commented on GitHub (Jul 2, 2025):

A patch is currently in progress to remove that fetching process, but to add further clarification:
the message is purely informational, and since the process runs in the background, there’s absolutely no need to wait for it to complete.

<!-- gh-comment-id:3027026402 --> @ltdrdata commented on GitHub (Jul 2, 2025): A patch is currently in progress to remove that fetching process, but to add further clarification: the message is purely informational, and since the process runs in the background, there’s absolutely no need to wait for it to complete.
Author
Owner

@mrwiora commented on GitHub (Jul 8, 2025):

@ltdrdata basically you are right with your assumptions, that it is an optional call, but fact is, that the startup is extremly long (>5min). but yes, the webinterface and all functions are then available

<!-- gh-comment-id:3048498999 --> @mrwiora commented on GitHub (Jul 8, 2025): @ltdrdata basically you are right with your assumptions, that it is an optional call, but fact is, that the startup is extremly long (>5min). but yes, the webinterface and all functions are then available
Author
Owner

@ltdrdata commented on GitHub (Jul 8, 2025):

@ltdrdata basically you are right with your assumptions, that it is an optional call, but fact is, that the startup is extremly long (>5min). but yes, the webinterface and all functions are then available

Does that mean the UI is unusable while the fetch is hanging?

<!-- gh-comment-id:3050495916 --> @ltdrdata commented on GitHub (Jul 8, 2025): > @ltdrdata basically you are right with your assumptions, that it is an optional call, but fact is, that the startup is extremly long (>5min). but yes, the webinterface and all functions are then available Does that mean the UI is unusable while the fetch is hanging?
Author
Owner

@mrwiora commented on GitHub (Jul 9, 2025):

correct. the step to reproduce this is the complete block of internet access. IPs are assigned.

<!-- gh-comment-id:3051256738 --> @mrwiora commented on GitHub (Jul 9, 2025): correct. the step to reproduce this is the complete block of internet access. IPs are assigned.
Author
Owner

@DmitryFX commented on GitHub (Aug 28, 2025):

+1 when trying to read the console errors, this fetching causes the scroll jump to end.

<!-- gh-comment-id:3231937678 --> @DmitryFX commented on GitHub (Aug 28, 2025): +1 when trying to read the console errors, this fetching causes the scroll jump to end.
Author
Owner

@CCpt5 commented on GitHub (Oct 21, 2025):

Is there an update on this? I also find it extremely annoying when trying to figure out why something failed to load (Re: scrolling up until it completes it's 2min of whatever is quickly scrolled back to the bottom due to the inevitable console printing)

<!-- gh-comment-id:3424311785 --> @CCpt5 commented on GitHub (Oct 21, 2025): Is there an update on this? I also find it extremely annoying when trying to figure out why something failed to load (Re: scrolling up until it completes it's 2min of whatever is quickly scrolled back to the bottom due to the inevitable console printing)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Comfy-Org/ComfyUI-Manager#820
No description provided.