[PR #2680] Fix for private registry channel #2688

New issue

Open

opened 2026-10-28 21:11:48 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-28 21:11:48 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/ComfyUI-Manager/pull/2680
Author: @Stefano-retinize
Created: 3/9/2026
Status: 🔄 Open

Base: main ← Head: main

📝 Commits (1)

03ecc06 Fix for private channel

📊 Changes

1 file changed (+42 additions, -4 deletions)

View changed files

📝 glob/manager_core.py (+42 -4)

📄 Description

Motivation and Context
We are a company using ComfyUI extensively to develop new products. While the ComfyUI-Manager is excellent for handling public nodes, we needed a way to set our own private channels to securely upload, distribute, and manage our internal, proprietary custom nodes across our team.

This PR extends the channel management logic to seamlessly support private and local channel URLs, allowing teams to maintain their own internal registries without conflicting with the DEFAULT_CHANNEL.

Key Changes

Dynamic Channel Resolution: Updated normalize_channel() and get_channel_dict() in manager_core.py to better handle custom, private, and local channel endpoints alongside the default public registry.
Config & Template Updates: Ensured that custom channel_url configurations are correctly parsed, cached, and respected during node fetching and updates.
Network & Security Handling: Integrated existing security level checks and SSL bypass configurations to ensure private endpoints (which may be behind corporate firewalls or VPNs) can be accessed reliably.
Robust Fallbacks: Maintained backward compatibility and fallback mechanisms for users who remain strictly on the default public channel.

How to Test

Update config.ini or channels.list to point to a private repository/URL hosting a custom node list.
Launch ComfyUI and open the Manager.
Verify that the internal nodes from the private channel populate correctly in the node list.
Install a private node and verify that it pulls the expected repository securely.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)

[x] New feature (non-breaking change which adds functionality)

[ ] Breaking change (fix or feature that would cause existing functionality to change)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/ComfyUI-Manager/pull/2680 **Author:** [@Stefano-retinize](https://github.com/Stefano-retinize) **Created:** 3/9/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`03ecc06`](https://github.com/Comfy-Org/ComfyUI-Manager/commit/03ecc06e96434c3de919c6b104374eb9a6afe318) Fix for private channel ### 📊 Changes **1 file changed** (+42 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `glob/manager_core.py` (+42 -4) </details> ### 📄 Description **Motivation and Context** We are a company using ComfyUI extensively to develop new products. While the ComfyUI-Manager is excellent for handling public nodes, we needed a way to set our own private channels to securely upload, distribute, and manage our internal, proprietary custom nodes across our team. This PR extends the channel management logic to seamlessly support private and local channel URLs, allowing teams to maintain their own internal registries without conflicting with the DEFAULT_CHANNEL. **Key Changes** 1. Dynamic Channel Resolution: Updated normalize_channel() and get_channel_dict() in manager_core.py to better handle custom, private, and local channel endpoints alongside the default public registry. 2. Config & Template Updates: Ensured that custom channel_url configurations are correctly parsed, cached, and respected during node fetching and updates. 3. Network & Security Handling: Integrated existing security level checks and SSL bypass configurations to ensure private endpoints (which may be behind corporate firewalls or VPNs) can be accessed reliably. 4. Robust Fallbacks: Maintained backward compatibility and fallback mechanisms for users who remain strictly on the default public channel. **How to Test** 1. Update config.ini or channels.list to point to a private repository/URL hosting a custom node list. 2. Launch ComfyUI and open the Manager. 3. Verify that the internal nodes from the private channel populate correctly in the node list. 4. Install a private node and verify that it pulls the expected repository securely. **Types of changes** [ ] Bug fix (non-breaking change which fixes an issue) [x] New feature (non-breaking change which adds functionality) [ ] Breaking change (fix or feature that would cause existing functionality to change) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-10-28 21:11:48 +00:00

bsakaguchi referenced this issue

2026-10-28 21:11:51 +00:00

[PR #2688] [CLOSED] Add Send-To-ComfyUI node #2693