mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
Gemini's setup can't finish #128
Reference in New Issue
Block a user
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?
Originally created by @Sanuki-073 on GitHub (Mar 27, 2025).
Self Checks
Dify version
1.1.3
Cloud or Self Hosted
Cloud
Steps to reproduce
Set up gemini in model provider
✔️ Expected Behavior
Finish the setup.
❌ Actual Behavior
Set up is not completed by 504 Error.
@dosubot[bot] commented on GitHub (Mar 27, 2025):
I found a similar open issue related to a 504 Gateway error during plugin authorization. The suggested solutions include:
Check Network Connectivity: Ensure there are no network issues between your setup and the endpoint. Verify that the endpoint is accessible and not blocked by any firewall or network restrictions.
Server Load and Timeout Settings: Check if the server handling the request is under heavy load and consider increasing the timeout settings. For Dify's cloud setup, it's recommended to set the
GUNICORN_TIMEOUTto 360 seconds to support longer connection times [1][2].Configuration Review: Double-check the configuration settings for Gemini in the model provider to ensure they are correct.
Logs and Monitoring: Review the logs for any errors or warnings that might provide more insight into the issue. Utilize monitoring tools like Opik and Langfuse to observe the behavior of your setup and identify potential issues [3][4].
These steps might help resolve the 504 error you're encountering during the Gemini setup.
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
@crazywoola commented on GitHub (Mar 27, 2025):
Please downgrade the plugin version to
0.0.7.The problem is introduced in the latest version
0.0.8.Our cloud env use lambda to deploy plugins, which doesn't have the permission to write files.
@Sanuki-073 commented on GitHub (Mar 27, 2025):
@crazywoola
Thank you for your response!
However, downgrading did not help resolve the issue.
Ultimately, I was able to solve it by building the gemini from the official package myself and uploading the file to cloud from my local environment.
@shoppingjaws commented on GitHub (Mar 27, 2025):
Okay, I will try to debug in this weekend #556