langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Dify1.9.1 ComfyUI Authorization failed #745

New Issue
Closed
opened 2026-02-16 10:20:22 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:20:22 -05:00
Owner
Copy Link
Copy Source

Originally created by @zhangxiaotian-China on GitHub (Oct 22, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues Dify issues & Dify Official Plugins, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.1

Plugin version

0.3.2、0.2.5

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Authorization process prompts error：
req_id: cfcd34cdf8 PluginInvokeError: {"args":{},"error_type":"ToolProviderCredentialValidationError","message":"can not connect to ws://192.168.2.201:8188/ws?clientId=test123. Error: Connection to remote host was lost."}
Image

The ComfyUI service is also normal and can be opened correctly when accessed in a browser

Image

The problem occurred after the upgrade of Dify, the previous version of Dify was 1.7. x

✔️ Error log

No response

Originally created by @zhangxiaotian-China on GitHub (Oct 22, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.1 ### Plugin version 0.3.2、0.2.5 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce Authorization process prompts error： req_id: cfcd34cdf8 PluginInvokeError: {"args":{},"error_type":"ToolProviderCredentialValidationError","message":"can not connect to ws://192.168.2.201:8188/ws?clientId=test123. Error: Connection to remote host was lost."} <img width="1351" height="895" alt="Image" src="https://github.com/user-attachments/assets/d5a55245-4a14-49d0-b923-781fc1db2abd" /> The ComfyUI service is also normal and can be opened correctly when accessed in a browser <img width="1269" height="658" alt="Image" src="https://github.com/user-attachments/assets/d9d03eb7-a8a7-4665-9fd9-2593f8caa93a" /> **The problem occurred after the upgrade of Dify, the previous version of Dify was 1.7. x** ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:20:22 -05:00
yindo closed this issue 2026-02-16 10:20:22 -05:00
yindo commented 2026-02-16 10:20:22 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 22, 2025):

Hi @zhangxiaotian-China! I'm Dosu and I’m helping the dify-official-plugins team.

Dify 1.9.1 introduced stricter credential validation and compliance checks for plugins, including ComfyUI. This means credentials are now checked for existence and policy compliance before use, and any missing or invalid credentials can cause authorization failures—even if the service is accessible in a browser. The new logic also surfaces clearer error messages and may block actions for unavailable credentials, which could explain the ToolProviderCredentialValidationError you're seeing after the upgrade [source].

To troubleshoot: double-check that your ComfyUI plugin configuration (URLs, API keys, and credential types) matches the expected format and that all credentials are valid and present in the Dify database. Also, ensure there are no network/firewall issues blocking WebSocket connections from Dify to ComfyUI, as browser access does not guarantee plugin connectivity. If you have multiple credentials, make sure none are invalid or missing, as Dify now checks all available credentials for compliance.

If the issue persists, try enabling debug logs for more detailed error output, test with a fresh credential, or revert to a previous plugin version to isolate the root cause.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Oct 22, 2025): <!-- Greeting --> Hi @zhangxiaotian-China! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. <!-- Answer --> Dify 1.9.1 introduced stricter credential validation and compliance checks for plugins, including ComfyUI. This means credentials are now checked for existence and policy compliance before use, and any missing or invalid credentials can cause authorization failures—even if the service is accessible in a browser. The new logic also surfaces clearer error messages and may block actions for unavailable credentials, which could explain the ToolProviderCredentialValidationError you're seeing after the upgrade [[source](https://github.com/langgenius/dify/pull/25151)]. To troubleshoot: double-check that your ComfyUI plugin configuration (URLs, API keys, and credential types) matches the expected format and that all credentials are valid and present in the Dify database. Also, ensure there are no network/firewall issues blocking WebSocket connections from Dify to ComfyUI, as browser access does not guarantee plugin connectivity. If you have multiple credentials, make sure none are invalid or missing, as Dify now checks all available credentials for compliance. If the issue persists, try enabling debug logs for more detailed error output, test with a fresh credential, or revert to a previous plugin version to isolate the root cause. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/6b7b8df1-f5b5-461b-9364-b00891de21c8?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6b7b8df1-f5b5-461b-9364-b00891de21c8?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6b7b8df1-f5b5-461b-9364-b00891de21c8?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6b7b8df1-f5b5-461b-9364-b00891de21c8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6b7b8df1-f5b5-461b-9364-b00891de21c8?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6b7b8df1-f5b5-461b-9364-b00891de21c8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6b7b8df1-f5b5-461b-9364-b00891de21c8?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1913)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#745
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?