langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

github PluginInvokeError #415

New Issue
Closed
opened 2026-02-16 10:19:21 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 10:19:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @kfchandsome on GitHub (Jul 2, 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 search for existing issues, 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.5

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

PluginInvokeError: {"args":{},"error_type":"ToolProviderCredentialValidationError","message":"GitHub API Key and Api Version is invalid. HTTPSConnectionPool(host='api.github.com', port=443): Max retries exceeded with url: /search/users?q=charli117 (Caused by NewConnectionError('\u003curllib3.connection.HTTPSConnection object at 0x7fbc1c491310\u003e: Failed to establish a new connection: [Errno 111] Connection refused'))"}

Image Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @kfchandsome on GitHub (Jul 2, 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 [search for existing issues](https://github.com/langgenius/dify/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.5 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce PluginInvokeError: {"args":{},"error_type":"ToolProviderCredentialValidationError","message":"GitHub API Key and Api Version is invalid. HTTPSConnectionPool(host='api.github.com', port=443): Max retries exceeded with url: /search/users?q=charli117 (Caused by NewConnectionError('\u003curllib3.connection.HTTPSConnection object at 0x7fbc1c491310\u003e: Failed to establish a new connection: [Errno 111] Connection refused'))"} <img width="1604" alt="Image" src="https://github.com/user-attachments/assets/170c8d97-d476-48e2-912c-feb4a3e03aac" /> <img width="1446" alt="Image" src="https://github.com/user-attachments/assets/5bace9ac-31f0-43c0-882e-44c68622fb21" /> ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-16 10:19:21 -05:00
yindo commented 2026-02-16 10:19:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 2, 2025):

The error you're seeing, ToolProviderCredentialValidationError, can be triggered by either invalid GitHub credentials (API key or version) or by network issues that prevent Dify from reaching the GitHub API. In your case, the "connection refused" part of the error suggests a network connectivity problem, not just a credential issue.

Here's what you can do:

  1. Double-check that your GitHub API key and API version are entered correctly in the plugin configuration.
  2. Test your API key outside of Dify (for example, using curl or Postman) to make sure it works and has the right permissions.
  3. From inside your Docker container, try to ping or curl https://api.github.com to confirm network access. If you get a connection refused or timeout, check your Docker network settings, firewall, or proxy configuration.
  4. Review any firewall or proxy rules that might block outgoing HTTPS connections from your container.
  5. Check Dify logs for more detailed error messages during the plugin invocation.

The Dify codebase treats any failure to reach the GitHub API (including network errors) as a credential validation error, so you may see this message even if your credentials are correct but the network is blocked or misconfigured. There’s no extra logic to distinguish between these cases in the current version (source, more).

If you confirm your credentials are valid and the network is open, but the error persists, let me know what you find from the above steps and I can help dig deeper.

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 (Jul 2, 2025): <!-- Answer --> The error you're seeing, ToolProviderCredentialValidationError, can be triggered by either invalid GitHub credentials (API key or version) or by network issues that prevent Dify from reaching the GitHub API. In your case, the "connection refused" part of the error suggests a network connectivity problem, not just a credential issue. Here's what you can do: 1. Double-check that your GitHub API key and API version are entered correctly in the plugin configuration. 2. Test your API key outside of Dify (for example, using curl or Postman) to make sure it works and has the right permissions. 3. From inside your Docker container, try to ping or curl https://api.github.com to confirm network access. If you get a connection refused or timeout, check your Docker network settings, firewall, or proxy configuration. 4. Review any firewall or proxy rules that might block outgoing HTTPS connections from your container. 5. Check Dify logs for more detailed error messages during the plugin invocation. The Dify codebase treats any failure to reach the GitHub API (including network errors) as a credential validation error, so you may see this message even if your credentials are correct but the network is blocked or misconfigured. There’s no extra logic to distinguish between these cases in the current version ([source](https://github.com/langgenius/dify/blob/68f41bbaa804a03abc046d0df484c1edc50f8066/api/core/tools/plugin_tool/provider.py), [more](https://github.com/langgenius/dify/blob/68f41bbaa804a03abc046d0df484c1edc50f8066/api/core/plugin/impl/tool.py)). If you confirm your credentials are valid and the network is open, but the error persists, let me know what you find from the above steps and I can help dig deeper. <!-- 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/1aa45021-dc62-4c9b-8e82-7b2d1f477316?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1aa45021-dc62-4c9b-8e82-7b2d1f477316?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1aa45021-dc62-4c9b-8e82-7b2d1f477316?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1aa45021-dc62-4c9b-8e82-7b2d1f477316?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1aa45021-dc62-4c9b-8e82-7b2d1f477316?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1aa45021-dc62-4c9b-8e82-7b2d1f477316?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1aa45021-dc62-4c9b-8e82-7b2d1f477316?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/issues/21836)
yindo commented 2026-02-16 10:19:21 -05:00
Author
Owner
Copy Link
Copy Source

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

maybe caused by your proxy? Many users might be sharing the same proxy node, and GitHub could block that node.

@hjlarry commented on GitHub (Jul 2, 2025): maybe caused by your proxy? Many users might be sharing the same proxy node, and GitHub could block that node.
yindo commented 2026-02-16 10:19:22 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 20, 2025):

Hi, @kfchandsome. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a PluginInvokeError in Dify 1.5 (Docker self-hosted) related to invalid GitHub API credentials and connection refusal to api.github.com.
  • The error causes a ToolProviderCredentialValidationError.
  • Initial suggestions pointed to network connectivity issues beyond just invalid credentials.
  • Recommendations included verifying API key validity, network access from the Docker container, and firewall or proxy settings.
  • Additional input noted that proxy usage might be causing GitHub to block shared proxy nodes, requiring further network and proxy configuration checks.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If I do not receive a response within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 20, 2025): Hi, @kfchandsome. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a PluginInvokeError in Dify 1.5 (Docker self-hosted) related to invalid GitHub API credentials and connection refusal to api.github.com. - The error causes a ToolProviderCredentialValidationError. - Initial suggestions pointed to network connectivity issues beyond just invalid credentials. - Recommendations included verifying API key validity, network access from the Docker container, and firewall or proxy settings. - Additional input noted that proxy usage might be causing GitHub to block shared proxy nodes, requiring further network and proxy configuration checks. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If I do not receive a response within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
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
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#415
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?