Check the SSL Verification Bypass Option

Oct 13, 2025 by thesweetdesigns.com 41 views

Cannot Start ComfyUI with Latest ComfyUI-Manager (V3.30.5)

ComfyUI is a powerful and user-friendly interface for managing and customizing various applications. However, users have reported issues with starting ComfyUI after updating to the latest ComfyUI-Manager (V3.30.5). In this article, we will explore the possible causes of this issue and provide a step-by-step guide to resolve it.

The error log provided by the user is as follows:

[START] Security scan
[DONE] Security scan
## ComfyUI-Manager: installing dependencies done.
** ComfyUI startup time: 2025-03-12 15:47:29.922
** Platform: Linux
** Python version: 3.12.5 | Intel Corporation | (main, Sep  9 2024, 23:35:37) [GCC 14.1.0]
** Python executable: /user/comfy_env/bin/python
** ComfyUI Path: /user/ComfyUI
** ComfyUI Base Folder Path: /user/ComfyUI
** User directory: /user/ComfyUI/user
** ComfyUI-Manager config path: /user/ComfyUI/user/default/ComfyUI-Manager/config.ini
** Log path: /user/ComfyUI/user/comfyui.log
[ComfyUI-Manager] WARN: Unsafe - SSL verification bypass option is Enabled. (see /user/ComfyUI/user/default/ComfyUI-Manager/config.ini)

Prestartup times for custom nodes:
   1.6 seconds: /user/ComfyUI/custom_nodes/ComfyUI-Manager

Set cuda device to: 2
Checkpoint files will always be loaded safely.
Total VRAM 14918 MB, total RAM 773491 MB
pytorch version: 2.6.0+cu124
xformers version: 0.0.29.post3
Set vram state to: NORMAL_VRAM
Device: cuda:0 Tesla T4 : cudaMallocAsync
Using xformers attention
ComfyUI version: 0.3.26
ComfyUI frontend version: 1.11.8
[Prompt Server] web root: /user/comfy_env/lib/python3.12/site-packages/comfyui_frontend_package/static
For direct API calls, use token=####################masked####################################
/user/ComfyUI/custom_nodes/comfyui-sentinel/utils/config.py:26: UserWarning: The SECRET_KEY environment variable is not set. A random key will be used for this session. This will cause all users to log out on server restart.
  warnings.warn(
### Loading: ComfyUI-Manager (V3.30.5)
[ComfyUI-Manager] network_mode: none
### ComfyUI Revision: 3254 [2330754b] *DETACHED | Released on '2025-03-11'

Import times for custom nodes:
   0.0 seconds: /user/ComfyUI/custom_nodes/ComfyUI-MultiGPU
   0.0 seconds: /user/ComfyUI/custom_nodes/websocket_image_save.py
   0.0 seconds: /user/ComfyUI/custom_nodes/comfyui-sentinel
   0.0 seconds: /user/ComfyUI/custom_nodes/ComfyUI-Manager
   0.1 seconds: /user/ComfyUI/custom_nodes/ComfyUI-Login
   0.1 seconds: /user/ComfyUI/custom_nodes/ComfyUI-WanVideoWrapper

Starting server

To see the GUI go to: http://127.0.0.1:8188
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/alter-list.json
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/model-list.json
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/custom-node-list.json
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/github-stats.json
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/extension-node-map.json
FETCH ComfyRegistry Data: 5/78
FETCH ComfyRegistry Data: 10/78
FETCH ComfyRegistry Data: 15/78
FETCH ComfyRegistry Data: 20/78
FETCH ComfyRegistry Data: 25/78
FETCH ComfyRegistry Data: 30/78
FETCH ComfyRegistry Data: 35/78
FETCH ComfyRegistry Data: 40/78
FETCH ComfyRegistry Data: 45/78
FETCH ComfyRegistry Data: 50/78
FETCH ComfyRegistry Data: 55/78
FETCH ComfyRegistry Data: 60/78
FETCH ComfyRegistry Data: 65/78
FETCH ComfyRegistry Data: 70/78
FETCH ComfyRegistry Data: 75/78
FETCH ComfyRegistry Data [DONE]
[ComfyUI-Manager] default cache updated: https://api.comfy.org/nodes
nightly_channel: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/remote
[ComfyUI-Manager] An invalid channel was used: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main
Exception in thread Thread-1 (<lambda>):
Traceback (most recent call last):
  File "/u/cd3ess/star/intelpython3/lib/python3.12/threading.py", line 1075, in _bootstrap_inner
    self.run()
  File "/u/cd3ess/star/intelpython3/lib/python3.12/threading.py", line 1012, in run
    self._target(*self._args, **self._kwargs)
  File "/user/ComfyUI/custom_nodes/ComfyUI-Manager/glob/manager_server.py", line 1746, in <lambda>
    threading.Thread(target=lambda: asyncio.run(default_cache_update())).start()
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/u/cd3ess/star/intelpython3/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/u/cd3ess/star/intelpython3/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/u/cd3ess/star/intelpython3/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/user/ComfyUI/custom_nodes/ComfyUI-Manager/glob/manager_server.py", line 1736, in default_cache_update
    await core.unified_manager.get_custom_nodes(channel_url, 'remote')
  File "/user/ComfyUI/custom_nodes/ComfyUI-Manager/glob/manager_core.py", line 812, in get_custom_nodes
    nodes = await self.load_nightly(channel, mode)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/user/ComfyUI/custom_nodes/ComfyUI-Manager/glob/manager_core.py", line 782, in load_nightly
    raise InvalidChannel(channel_url)
manager_core.InvalidChannel: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main

Based on the error log, the possible causes of this issue are:

Invalid Channel URL: The error message indicates that an invalid channel URL was used. This could be due to a misconfigured or outdated channel URL in the ComfyUI-Manager configuration.
SSL Verification Bypass: The error log shows that the SSL verification bypass option is enabled. This could be causing issues with the ComfyUI-Manager's ability to connect to the channel URL.
Custom Node Issues: The error log mentions that there are issues with custom nodes, specifically with the ComfyUI-Manager's ability to load custom nodes from the channel URL.

To resolve this issue, follow these steps:

Step 1: Check the Channel URL

Verify the Channel URL: Check the ComfyUI-Manager configuration file (config.ini) to ensure that the channel URL is correct and up-to-date.
Update the Channel URL: If the channel URL is outdated or incorrect, update it to the latest version.

Step 2: Disable SSL Verification Bypass

Check the SSL Verification Bypass Option: Check the ComfyUI-Manager configuration file (config.ini) to see if the SSL verification bypass option is enabled.
Disable the SSL Verification Bypass Option: If the SSL verification bypass option is enabled, disable it to ensure that ComfyUI-Manager can connect to the channel URL securely.

Step 3: Check Custom Node Issues

Verify Custom Node Configuration: Check the custom node configuration files to ensure that they are correctly configured and up-to-date.
Update Custom Node Configuration: If there are issues with custom node configuration,
Q&A: Cannot Start ComfyUI with Latest ComfyUI-Manager (V3.30.5)

Q: What is the issue with starting ComfyUI with the latest ComfyUI-Manager (V3.30.5)?

A: The issue is caused by an invalid channel URL, which is used by ComfyUI-Manager to connect to the channel. This can be due to a misconfigured or outdated channel URL in the ComfyUI-Manager configuration.

Q: What are the possible causes of this issue?

A: The possible causes of this issue are:

Invalid Channel URL: The error message indicates that an invalid channel URL was used. This could be due to a misconfigured or outdated channel URL in the ComfyUI-Manager configuration.
SSL Verification Bypass: The error log shows that the SSL verification bypass option is enabled. This could be causing issues with the ComfyUI-Manager's ability to connect to the channel URL.
Custom Node Issues: The error log mentions that there are issues with custom nodes, specifically with the ComfyUI-Manager's ability to load custom nodes from the channel URL.

Q: How can I resolve this issue?

A: To resolve this issue, follow these steps:

Step 1: Check the Channel URL

Verify the Channel URL: Check the ComfyUI-Manager configuration file (config.ini) to ensure that the channel URL is correct and up-to-date.
Update the Channel URL: If the channel URL is outdated or incorrect, update it to the latest version.

Step 2: Disable SSL Verification Bypass

Check the SSL Verification Bypass Option: Check the ComfyUI-Manager configuration file (config.ini) to see if the SSL verification bypass option is enabled.
Disable the SSL Verification Bypass Option: If the SSL verification bypass option is enabled, disable it to ensure that ComfyUI-Manager can connect to the channel URL securely.

Step 3: Check Custom Node Issues

Verify Custom Node Configuration: Check the custom node configuration files to ensure that they are correctly configured and up-to-date.
Update Custom Node Configuration: If there are issues with custom node configuration, update it to the latest version.

Q: What are the benefits of resolving this issue?

A: Resolving this issue will allow you to start ComfyUI with the latest ComfyUI-Manager (V3.30.5) and ensure that it functions correctly. This will also prevent any potential issues with custom nodes and ensure that ComfyUI-Manager can connect to the channel URL securely.

Q: How can I prevent this issue from occurring in the future?

A: To prevent this issue from occurring in the future, ensure that you:

Regularly Update the Channel URL: Regularly update the channel URL to ensure that it is correct and up-to-date.
Disable SSL Verification Bypass: Disable the SSL verification bypass option to ensure that ComfyUI-Manager can connect to the channel URL securely.
Verify Custom Node Configuration: Regularly verify custom node configuration to ensure that it is correctly configured and up-to-date.

By following these steps and best practices, you can prevent this issue from occurring in the future and ensure that ComfyUI functions correctly with the latest ComfyUI-Manager (V3.30.5).