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

Jina Reader API issue #8202

New Issue
Closed
opened 2026-02-21 18:24:27 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:24:27 -05:00
Owner
Copy Link
Copy Source

Originally created by @mijoro7 on GitHub (Feb 12, 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

latest

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  • Updating Jina AI reader API key with a new one.
  • The key was updated successfully.
  • API key needs to be updated as free quota was reached, giving 402 error.
  • So updated with a new one but it still gives me the same 402 error as like in this picture: https://i.imgur.com/pRuwsyw.png
  • It should have been updated as the key is already a new one.

✔️ Expected Behavior

Jina reader with a new API key should work and not give a 402 error quota reached anymore.
So where else should I update the new key to make it worked? (already did both in the workflow itself and in the settings too).

❌ Actual Behavior

https://i.imgur.com/pRuwsyw.png

Originally created by @mijoro7 on GitHub (Feb 12, 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 latest ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce - Updating Jina AI reader API key with a new one. - The key was updated successfully. - API key needs to be updated as free quota was reached, giving 402 error. - So updated with a new one but it still gives me the same 402 error as like in this picture: https://i.imgur.com/pRuwsyw.png - It should have been updated as the key is already a new one. ### ✔️ Expected Behavior Jina reader with a new API key should work and not give a 402 error quota reached anymore. So where else should I update the new key to make it worked? (already did both in the workflow itself and in the settings too). ### ❌ Actual Behavior https://i.imgur.com/pRuwsyw.png
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:24:27 -05:00
yindo closed this issue 2026-02-21 18:24:27 -05:00
yindo commented 2026-02-21 18:24:27 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 12, 2025):

@mijoro7 Hello there! I'm here to help you with bug fixes, answer questions, and guide you on how to become a contributor. Let's tackle this issue together while we wait for a human maintainer.

To resolve the issue with the Jina AI reader API key still giving a 402 error after updating, ensure that the new API key is correctly updated in all necessary locations. Here are the steps you can follow:

  1. Configuration in Dify Interface: Make sure you have updated the API key in the Dify interface by navigating to the DataSource page and configuring the Jina Reader settings [1].

  2. Configuration Files: Check the jina.yaml file located at api/core/tools/provider/builtin/jina/jina.yaml in the Dify codebase. Ensure that the API key is correctly specified in the credentials_for_provider section [2].

  3. Environment Variables: Verify that any environment variables related to the Jina AI reader API key are updated. The placeholder for the API key is specified as apiKeyPlaceholder: 'Clave de API de jina.ai' in the code [3].

If the issue persists after these checks, consider restarting the Dify application to ensure that all changes are applied. Additionally, verify that there are no caching mechanisms that might be affecting the update, although no specific caching mechanisms have been identified 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 | Other | Bug Report

@dosubot[bot] commented on GitHub (Feb 12, 2025): <!-- Greeting --> @mijoro7 Hello there! I'm here to help you with bug fixes, answer questions, and guide you on how to become a contributor. Let's tackle this issue together while we wait for a human maintainer. <!-- Answer --> To resolve the issue with the Jina AI reader API key still giving a 402 error after updating, ensure that the new API key is correctly updated in all necessary locations. Here are the steps you can follow: 1. **Configuration in Dify Interface**: Make sure you have updated the API key in the Dify interface by navigating to the **DataSource** page and configuring the Jina Reader settings <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/knowledge-base/sync-from-website.md)</sup>. 2. **Configuration Files**: Check the `jina.yaml` file located at `api/core/tools/provider/builtin/jina/jina.yaml` in the Dify codebase. Ensure that the API key is correctly specified in the `credentials_for_provider` section <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/jina/jina.yaml)</sup>. 3. **Environment Variables**: Verify that any environment variables related to the Jina AI reader API key are updated. The placeholder for the API key is specified as `apiKeyPlaceholder: 'Clave de API de jina.ai'` in the code <sup>[[3]](https://github.com/langgenius/dify/blob/main/web/i18n/pt-BR/dataset-creation.ts)</sup>. If the issue persists after these checks, consider restarting the Dify application to ensure that all changes are applied. Additionally, verify that there are no caching mechanisms that might be affecting the update, although no specific caching mechanisms have been identified 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/5529a291-fc61-4276-afd6-877a739f47ea?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/5529a291-fc61-4276-afd6-877a739f47ea?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/5529a291-fc61-4276-afd6-877a739f47ea?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/5529a291-fc61-4276-afd6-877a739f47ea?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5529a291-fc61-4276-afd6-877a739f47ea?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/5529a291-fc61-4276-afd6-877a739f47ea?feedback_type=other) | [Bug Report](https://app.dosu.dev/response-feedback/5529a291-fc61-4276-afd6-877a739f47ea?feedback_type=bug_report)</sup>
yindo commented 2026-02-21 18:24:28 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 12, 2025):

There are 2 places where you can modify the API key

  • The system model provider
  • The tool 's configuration page
    I think you missed the second one.
Image
@crazywoola commented on GitHub (Feb 12, 2025): There are 2 places where you can modify the API key - The system model provider - The tool 's configuration page I think you missed the second one. <img width="1381" alt="Image" src="https://github.com/user-attachments/assets/ec3a7ed8-666c-41b0-b1c9-aaf75bfb47b6" />
yindo commented 2026-02-21 18:24:28 -05:00
Author
Owner
Copy Link
Copy Source

@mijoro7 commented on GitHub (Feb 12, 2025):

Thanks so much. You're right I forgot to update the one inside "Tools" config

@mijoro7 commented on GitHub (Feb 12, 2025): Thanks so much. You're right I forgot to update the one inside "Tools" config
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 🐞 bug 🤔 cant-reproduce
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#8202
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?