Plugin Jina.ai cannot be configed

[btbxbob]

Self Checks

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

Dify version

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. install jina.ai plugin from market
2. find jina.ai in tools, click it, select "auth"

✔️ Expected Behavior

pop up a dialog to input key

❌ Actual Behavior

shows error: Internel Server Error. in my backend log shows:

plugin_daemon-1  | 2025/02/14 07:42:23 /app/internal/db/pgsql.go:269 SLOW SQL >= 200ms
plugin_daemon-1  | [251.469ms] [rows:3] SELECT * FROM "ai_model_installations" WHERE tenant_id = 'd4a56375-f696-46d7-ad6c-0097451ada37' LIMIT 256
p
plugin_daemon-1  | 2025/02/14 07:42:28 /app/internal/db/pgsql.go:259 record not found
plugin_daemon-1  | [0.428ms] [rows:0] SELECT * FROM "tool_installations" WHERE tenant_id = 'd4a56375-f696-46d7-ad6c-0097451ada37' AND plugin_id = 'langgenius/jina' ORDER BY "tool_installations"."id" LIMIT 1

[dosubot[bot]]

@btbxbob Hello there! I'm here to help you with bug fixes, answer questions, and guide you to become a contributor. Let's work together to solve this issue!

A similar issue was reported regarding an "Internal Server Error" when interacting with plugins in Dify. Common causes include DNS resolution issues, especially when the system cannot resolve the hostname due to restrictions like those imposed by the Great Firewall (GFW). This can result in errors such as:

Request to Plugin Daemon Service failed
urllib3.exceptions.NameResolutionError: Failed to resolve 'plugin' ([Errno -2] Name or service not known)

To resolve this, ensure proper DNS settings or use a VPN to bypass such restrictions ^[1].

Additionally, for troubleshooting internal server errors, it is recommended to reset the encryption key pair and ensure that 'localhost' or '127.0.0.1' is replaced with 'host.docker.internal' in your Dify configuration for proper Docker container service access ^[2].

Regarding the slow SQL query you mentioned, it might be helpful to investigate the database performance and optimize the query or database configuration to address the slow execution time. Unfortunately, specific logging mechanisms for diagnosing slow SQL queries in Dify 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}

[btbxbob]

this problem seams resolved in 0.0.3, thanks!