langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Try to acess Gemini thru my API, #12253

New Issue
Closed
opened 2026-02-21 19:06:35 -05:00 by yindo · 8 comments
yindo commented 2026-02-21 19:06:35 -05:00
Owner
Copy Link
Copy Source

Originally created by @WilsonVasc56 on GitHub (Mar 27, 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

Version 1.1.3

Cloud or Self Hosted

Cloud

Steps to reproduce

Using my GEMINI any models, was working until yesterday...

✔️ Expected Behavior

have some answers, any answer,

❌ Actual Behavior

just take forever

Image

Originally created by @WilsonVasc56 on GitHub (Mar 27, 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 Version 1.1.3 ### Cloud or Self Hosted Cloud ### Steps to reproduce Using my GEMINI any models, was working until yesterday... ### ✔️ Expected Behavior have some answers, any answer, ### ❌ Actual Behavior just take forever ![Image](https://github.com/user-attachments/assets/e7d92851-a7a9-4f3a-9e7a-1345794bcf80)
yindo added the 🐞 bugcloud labels 2026-02-21 19:06:35 -05:00
yindo closed this issue 2026-02-21 19:06:35 -05:00
yindo commented 2026-02-21 19:06:35 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 27, 2025):

Hello @WilsonVasc56! I'm here to help you with any bugs, questions, or contributions. Let's work together to solve the issue you're facing.

I found a similar issue that might be relevant to your situation. There was an issue titled "[google] Server Unavailable Error, 504 Deadline Exceeded and Error: Minified React error #185" which was closed after a pull request fixed the problem by addressing a React.js error [1]. However, this might not directly relate to your current issue with the "PluginDaemonInnerError" and "failed to read response body: context deadline exceeded" error.

The "PluginDaemonInnerError" in Dify is triggered by a ConnectionError when trying to access the plugin service, which suggests a failure to establish a connection to the plugin management endpoint [2]. This could be related to network issues or service availability.

For the "context deadline exceeded" error, Dify's cloud version typically handles such errors by implementing a retry strategy with exponential backoff, but specific handling in the context of plugin invocation wasn't found in the available information [3].

You might want to check the network connectivity to the plugin service and ensure that there are no disruptions or configuration issues that could be causing the connection failure.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 27, 2025): <!-- Greeting --> Hello @WilsonVasc56! I'm here to help you with any bugs, questions, or contributions. Let's work together to solve the issue you're facing. <!-- Answer --> I found a similar issue that might be relevant to your situation. There was an issue titled "[google] Server Unavailable Error, 504 Deadline Exceeded and Error: Minified React error #185" which was closed after a pull request fixed the problem by addressing a React.js error <sup>[[1]](https://github.com/langgenius/dify/issues/4232)</sup>. However, this might not directly relate to your current issue with the "PluginDaemonInnerError" and "failed to read response body: context deadline exceeded" error. The "PluginDaemonInnerError" in Dify is triggered by a `ConnectionError` when trying to access the plugin service, which suggests a failure to establish a connection to the plugin management endpoint <sup>[[2]](https://github.com/langgenius/dify/issues/15835)</sup>. This could be related to network issues or service availability. For the "context deadline exceeded" error, Dify's cloud version typically handles such errors by implementing a retry strategy with exponential backoff, but specific handling in the context of plugin invocation wasn't found in the available information <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/node/http-request.md)</sup>. You might want to check the network connectivity to the plugin service and ensure that there are no disruptions or configuration issues that could be causing the connection failure. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/552308a0-8ac6-4d55-ac2a-26bfbfcbad1f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/552308a0-8ac6-4d55-ac2a-26bfbfcbad1f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/552308a0-8ac6-4d55-ac2a-26bfbfcbad1f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/552308a0-8ac6-4d55-ac2a-26bfbfcbad1f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/552308a0-8ac6-4d55-ac2a-26bfbfcbad1f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/552308a0-8ac6-4d55-ac2a-26bfbfcbad1f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/552308a0-8ac6-4d55-ac2a-26bfbfcbad1f?feedback_type=other)</sup>
yindo commented 2026-02-21 19:06:35 -05:00
Author
Owner
Copy Link
Copy Source

@WilsonVasc56 commented on GitHub (Mar 27, 2025):

@dosu we are connecting from different countries, USA and Brazil...same error

@WilsonVasc56 commented on GitHub (Mar 27, 2025): @dosu we are connecting from different countries, USA and Brazil...same error
yindo commented 2026-02-21 19:06:35 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 27, 2025):

The "PluginDaemonInnerError" and "context deadline exceeded" errors you're encountering could be related to network issues or service availability, especially when accessing from different geographical locations like the USA and Brazil. Here are a few steps you can take to troubleshoot and potentially resolve the issue:

  1. Check Network Connectivity: Ensure that there are no network disruptions or proxy settings that might be affecting the connection to the plugin service.

  2. Verify Service Status: Make sure that the plugin daemon service is running properly. If you're using Docker, check that all relevant containers are up and running.

  3. Adjust Timeout Settings: If the issue persists, consider increasing the timeout settings for plugin service requests. You can configure these settings in the .env file or docker-compose.yml as needed [1].

  4. Geographical Considerations: Network latency and routing issues can sometimes cause problems when accessing services from different countries. If possible, test the connection from a different network or location to see if the issue persists.

If these steps do not resolve the issue, it might be helpful to look into any specific network configurations required for accessing Dify's plugin service from different countries, although specific details on this were not found in the available information.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 27, 2025): <!-- Answer --> The "PluginDaemonInnerError" and "context deadline exceeded" errors you're encountering could be related to network issues or service availability, especially when accessing from different geographical locations like the USA and Brazil. Here are a few steps you can take to troubleshoot and potentially resolve the issue: 1. **Check Network Connectivity**: Ensure that there are no network disruptions or proxy settings that might be affecting the connection to the plugin service. 2. **Verify Service Status**: Make sure that the plugin daemon service is running properly. If you're using Docker, check that all relevant containers are up and running. 3. **Adjust Timeout Settings**: If the issue persists, consider increasing the timeout settings for plugin service requests. You can configure these settings in the `.env` file or `docker-compose.yml` as needed <sup>[[1]](https://github.com/langgenius/dify/issues/15082)</sup>. 4. **Geographical Considerations**: Network latency and routing issues can sometimes cause problems when accessing services from different countries. If possible, test the connection from a different network or location to see if the issue persists. If these steps do not resolve the issue, it might be helpful to look into any specific network configurations required for accessing Dify's plugin service from different countries, although specific details on this were not found in the available information. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/4edf35c2-02f5-4a78-8472-489ab5455e82?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4edf35c2-02f5-4a78-8472-489ab5455e82?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4edf35c2-02f5-4a78-8472-489ab5455e82?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4edf35c2-02f5-4a78-8472-489ab5455e82?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4edf35c2-02f5-4a78-8472-489ab5455e82?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4edf35c2-02f5-4a78-8472-489ab5455e82?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4edf35c2-02f5-4a78-8472-489ab5455e82?feedback_type=other)</sup>
yindo commented 2026-02-21 19:06:35 -05:00
Author
Owner
Copy Link
Copy Source

@WilsonVasc56 commented on GitHub (Mar 27, 2025):

@desu i will try and let you know, thanks...

@WilsonVasc56 commented on GitHub (Mar 27, 2025): @desu i will try and let you know, thanks...
yindo commented 2026-02-21 19:06:35 -05:00
Author
Owner
Copy Link
Copy Source

@WilsonVasc56 commented on GitHub (Mar 28, 2025):

@desu, try 4 differents locations 2 in USA and 2 in Brazil, different computersand different locations in each country , now the API is not even getting my new API key from google, not even saving it, so i don't thing is Network connection. All other Models are woring but Gemini...any more suggestions ?

@WilsonVasc56 commented on GitHub (Mar 28, 2025): @desu, try 4 differents locations 2 in USA and 2 in Brazil, different computersand different locations in each country , now the API is not even getting my new API key from google, not even saving it, so i don't thing is Network connection. All other Models are woring but Gemini...any more suggestions ?
yindo commented 2026-02-21 19:06:35 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 28, 2025):

Thank you for your patience regarding the issue with the Gemini model. For now, please try version 0.0.5, as I just tested it and confirmed that it works for Gemini models. You can also test other versions if you needed.
We will work on fixing and updating the Gemini provider in the future.
Please go to Plugin page at the right top corner or using the following link: https://cloud.dify.ai/plugins

Meanwhile, we are fixing it.

@crazywoola commented on GitHub (Mar 28, 2025): Thank you for your patience regarding the issue with the Gemini model. For now, please try version 0.0.5, as I just tested it and confirmed that it works for Gemini models. You can also test other versions if you needed. We will work on fixing and updating the Gemini provider in the future. Please go to Plugin page at the right top corner or using the following link: https://cloud.dify.ai/plugins Meanwhile, we are fixing it.
yindo commented 2026-02-21 19:06:36 -05:00
Author
Owner
Copy Link
Copy Source

@WilsonVasc56 commented on GitHub (Mar 28, 2025):

Yes it did work on 0.0.5 thanks and that's the only one that's workin .6 .7 and .8 none of them are working

@WilsonVasc56 commented on GitHub (Mar 28, 2025): Yes it did work on 0.0.5 thanks and that's the only one that's workin .6 .7 and .8 none of them are working
yindo commented 2026-02-21 19:06:36 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 28, 2025):

See https://github.com/langgenius/dify-official-plugins/pull/596

@crazywoola commented on GitHub (Mar 28, 2025): See https://github.com/langgenius/dify-official-plugins/pull/596
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label cloud 🐞 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#12253
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?