mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
Jina plugin invoke error #565
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 @qadeerikram-art on GitHub (Aug 19, 2025).
Self Checks
Dify version
1.7.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
I have workflow where i am getting data from knowledgebase when doing chat with chatbot. when i do chat with chatbot sometime it give me this error Jina plugin invoke error.
✔️ Expected Behavior
There should not be any error
❌ Actual Behavior
Getting error I have workflow where i am getting data from knowledgebase when doing chat with chatbot. when i do chat with chatbot sometime it give me this error Jina plugin invoke error.
@dosubot[bot] commented on GitHub (Aug 19, 2025):
A "Jina plugin invoke error" with a 403 Forbidden from the Jina API almost always points to an authentication or permission issue with your Jina API key or account configuration. In self-hosted Docker setups, this can also be caused by misconfigured environment variables or plugin settings. Double-check that your Jina API key is valid, has the necessary permissions, and is correctly set in the Dify plugin configuration UI. Make sure any required environment variables (like endpoint URLs) are set in your Docker
.envfile and that the containers have been restarted after changes. Similar issues in other plugins have been resolved by correcting API keys or environment variables and ensuring the correct protocol (http/https) is used in URLs. If the problem persists, enable debug logging in your Dify and Jina containers to capture more detailed error messages for further diagnosis. More details on error handling and troubleshooting can be found here and here.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@qadeerikram-art commented on GitHub (Aug 19, 2025):
What kind of jina configurations ? Jina key is valid that's why it's working otherwise it won't let me even do single chat. Earlier i was using 0.15 and now i have upgraded to 1.7.0. After upgrading its giving error and its random error. what i have to check in docker env or in jina configuration ?
@dosubot[bot] commented on GitHub (Aug 19, 2025):
After upgrading to Dify 1.7.0, there are a few key things to check for Jina plugin stability:
truein your.envand Docker config. It's required for Jina-based knowledge retrieval to work in 1.7.0. If it's missing or false, you can get random plugin errors."jina"is now"jinareader"or"langgenius/jina_tool/jina". If your database still has old provider names, you may see intermittent errors. Running the migration script updates these entries—if you skipped this, some KB nodes may still use the old format and fail randomly.See migration logic
config.api_keyand uses Bearer authentication.See details
r.jina.aiis allowed indocker/ssrf_proxy/squid.conf.template. If blocked, you can get 403 errors even with a valid key.See SSRF proxy config advice
SSRF_DEFAULT_TIME_OUTandHTTP_REQUEST_MAX_CONNECT_TIMEOUTin your.env(e.g., set to600).See timeout advice
If you still get random 403 errors after checking these, it's likely a migration or config propagation issue. Double-check your provider names in the DB, confirm the environment variable is set everywhere, and ensure the SSRF proxy isn't blocking Jina. Restart your containers after making changes.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@qadeerikram-art commented on GitHub (Aug 19, 2025):
ENABLE_WEBSITE_JINAREADER is true in env and no other keys are available. how to run migration to change jina to jinareader ? Could it be because of something else ? while running locally i am also getting this error
Run failed: [jina] Error: PluginInvokeError: {"args":{"description":"[models] Error: Client error '403 Forbidden' for url 'https://api.jina.ai/v1/rerank'\nFor more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403"},"error_type":"InvokeError","message":"models] Error: Client error '403 Forbidden' for url 'https://api.jina.ai/v1/rerank'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403"}
@dosubot[bot] commented on GitHub (Aug 19, 2025):
The "Jina plugin invoke error" with a 403 Forbidden from the Jina AI API in Dify (self-hosted Docker) is most often caused by one of these issues: an invalid or missing Jina API key, SSRF proxy blocking access to Jina endpoints, or network/configuration problems in Docker.
Here's a quick troubleshooting checklist:
Check your Jina API key: Make sure the API key is set correctly in your Dify plugin configuration and has the right permissions. The key is sent as a Bearer token in the Authorization header—if it's missing or invalid, you'll get a 403 error. See how the key is handled in the code.
Review SSRF proxy config: In Docker, all external API calls (including to Jina) go through the SSRF proxy (Squid). If the proxy blocks
r.jina.aiorapi.jina.ai, you'll get a 403. Updatedocker/ssrf_proxy/squid.conf.templateto allow access to these endpoints. More on this here.Increase timeouts: The default SSRF proxy timeouts (5 seconds) may be too low. Set
SSRF_DEFAULT_TIME_OUTandHTTP_REQUEST_MAX_CONNECT_TIMEOUTto higher values (e.g., 600) in your.envfile. Dify does not use.env.exampleautomatically—you must set these manually. Details here.Network access: Make sure your Docker containers can reach Jina's API endpoints. If your network restricts outbound traffic, plugin calls will fail.
Enable debug logging: Set
LOG_LEVEL=DEBUGand optionallyLOG_FILEin your.envto get more detailed logs. Check plugin daemon logs for the actual error returned by Jina.Recent Dify versions improved error messaging for plugin invocation errors, but the root cause (auth/network/config) must be fixed in your environment for the plugin to work see PR #22908.
If you update these configs and still see the error, check the logs for the exact response from Jina—sometimes the error message will tell you if it's a key, permission, or rate limit issue.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@qadeerikram-art commented on GitHub (Aug 19, 2025):
What's the solution here ?
@dosu
@dosubot[bot] commented on GitHub (Aug 19, 2025):
The 403 Forbidden "Jina plugin invoke error" in Dify is almost always caused by one of these: an invalid or missing Jina API key, SSRF proxy (Squid) blocking access to Jina endpoints, network restrictions, or too-short timeouts. Here’s how to solve it:
Double-check your Jina API key in the Dify plugin config. It must be present, valid, and have the right permissions. If the key is missing or wrong, you’ll get a 403 error. The key is sent as a Bearer token in the Authorization header—see how it’s handled in the code here.
Make sure your Docker SSRF proxy (Squid) allows outbound traffic to
r.jina.aiandapi.jina.ai. If not, you’ll get a 403. Updatedocker/ssrf_proxy/squid.conf.templateto allow these endpoints.Set
SSRF_DEFAULT_TIME_OUTandHTTP_REQUEST_MAX_CONNECT_TIMEOUTto higher values (like 600) in your.envfile. Dify doesn’t use.env.exampleautomatically—you must set these manually.Ensure your Docker containers can reach Jina’s API endpoints. If your network restricts outbound traffic, plugin calls will fail.
Set
LOG_LEVEL=DEBUGand (optionally)LOG_FILEin your.envto get detailed logs. Check the plugin daemon logs for the actual error from Jina—sometimes the error message will tell you if it’s a key, permission, or rate limit issue.After making changes, restart your Docker containers to apply the new settings.
If you still see the error, check the plugin daemon logs for the exact response from Jina. The error details will usually point to the root cause—invalid key, permission denied, or network block. Recent Dify versions improved error messaging for plugin invocation errors, so the logs should be more helpful now see PR #22908.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@qadeerikram-art commented on GitHub (Aug 19, 2025):
ENABLE_WEBSITE_JINAREADER is true. what if i set it to false ? there is no SSRF_DEFAULT_TIME_OUT and HTTP_REQUEST_MAX_CONNECT_TIMEOUT variable in env. how to view log file locally ?
@dosu
@dosubot[bot] commented on GitHub (Aug 19, 2025):
If you set ENABLE_WEBSITE_JINAREADER to false, the Jina Reader option will disappear from the website data source UI and "sync from website" via Jina will be disabled. In Dify 1.7.0, this flag must be true for Jina-based knowledge retrieval to work—if it's false or missing, you'll get random plugin errors, including the 403s you saw. The flag is required for both the UI and backend integration in this version, so keep it true unless you want to fully disable Jina Reader features and accept that related workflows will break or error out details.
For SSRF_DEFAULT_TIME_OUT and HTTP_REQUEST_MAX_CONNECT_TIMEOUT: if they're missing from your .env, just add them manually. Recommended value is 600 (seconds). Dify does not use .env.example automatically, so you must set these yourself reference.
To view logs locally in Docker: logs are stored by default at /app/logs/server.log inside the container. You can use docker-compose logs api or docker logs <CONTAINER_ID> to view them. You can also set LOG_FILE in your .env to customize the log file path, and mount /app/logs as a Docker volume if you want to access logs directly from your host instructions.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@qadeerikram-art commented on GitHub (Aug 19, 2025):
@dosubot[bot] commented on GitHub (Sep 4, 2025):
Hi, @qadeerikram-art. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!