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

Firecrawl and Jina Reader APIs don't work #7911

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

Originally created by @conflock on GitHub (Jan 27, 2025).

Originally assigned to: @crazywoola on GitHub.

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

0.15.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Both APIs for crawling websites, Firecrawl and Jina Reader don't work. Firecrawl throws an error "
Failed to start crawl job. Status code: 400. Error: Bad Request" and Jina Reader throws a Firecrawl Error (!!!). At the moment it is not possible to use websites as data source.

✔️ Expected Behavior

Crawl websites with external crawling APIs

❌ Actual Behavior

Both APIs throw errors

Originally created by @conflock on GitHub (Jan 27, 2025). Originally assigned to: @crazywoola on GitHub. ### 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 0.15.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Both APIs for crawling websites, Firecrawl and Jina Reader don't work. Firecrawl throws an error " Failed to start crawl job. Status code: 400. Error: Bad Request" and Jina Reader throws a Firecrawl Error (!!!). At the moment it is not possible to use websites as data source. ### ✔️ Expected Behavior Crawl websites with external crawling APIs ### ❌ Actual Behavior Both APIs throw errors
yindo added the 🐞 bugstale labels 2026-02-21 18:22:59 -05:00
yindo closed this issue 2026-02-21 18:22:59 -05:00
yindo commented 2026-02-21 18:23:00 -05:00
Author
Owner
Copy Link
Copy Source

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

Hello @flockton! I'm here to help you with any bugs, questions, or contributions you have while waiting for a human maintainer. Let's work together to solve this issue.

I found a similar unsolved discussion regarding the issue with the Firecrawl and Jina Reader APIs, which might be relevant to your situation. You can check it out here [1].

Regarding the errors you're encountering, there are a few potential causes to consider:

  1. Missing or Invalid Parameters: Ensure that all required parameters like url, options, and limit are correctly provided in your requests. Missing or invalid parameters can lead to a "Bad Request" error.

  2. Invalid Provider: Verify that the provider specified is either "firecrawl" or "jinareader". Any other value will result in an error.

  3. API Key Issues: Check that the API key is correctly configured and decrypted. An incorrect API key can cause authentication errors.

  4. Incorrect API Endpoint or Parameters: Make sure that the endpoints and parameters used in your requests are correct. Any mismatch can result in a 400 error.

These are some areas to investigate to resolve the issue. If you need further assistance, please provide more details about your configuration and the exact requests being made.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Jan 27, 2025): <!-- Greeting --> Hello @flockton! I'm here to help you with any bugs, questions, or contributions you have while waiting for a human maintainer. Let's work together to solve this issue. <!-- Answer --> I found a similar unsolved discussion regarding the issue with the Firecrawl and Jina Reader APIs, which might be relevant to your situation. You can check it out [here](https://github.com/langgenius/dify/discussions/8604) <sup>[[1]](https://github.com/langgenius/dify/discussions/8604)</sup>. Regarding the errors you're encountering, there are a few potential causes to consider: 1. **Missing or Invalid Parameters**: Ensure that all required parameters like `url`, `options`, and `limit` are correctly provided in your requests. Missing or invalid parameters can lead to a "Bad Request" error. 2. **Invalid Provider**: Verify that the provider specified is either "firecrawl" or "jinareader". Any other value will result in an error. 3. **API Key Issues**: Check that the API key is correctly configured and decrypted. An incorrect API key can cause authentication errors. 4. **Incorrect API Endpoint or Parameters**: Make sure that the endpoints and parameters used in your requests are correct. Any mismatch can result in a 400 error. These are some areas to investigate to resolve the issue. If you need further assistance, please provide more details about your configuration and the exact requests being made. <!-- 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/d939ba13-0bfb-4d06-bc82-282d69b5cb3b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/d939ba13-0bfb-4d06-bc82-282d69b5cb3b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/d939ba13-0bfb-4d06-bc82-282d69b5cb3b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/d939ba13-0bfb-4d06-bc82-282d69b5cb3b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d939ba13-0bfb-4d06-bc82-282d69b5cb3b?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/d939ba13-0bfb-4d06-bc82-282d69b5cb3b?feedback_type=other)</sup>
yindo commented 2026-02-21 18:23:00 -05:00
Author
Owner
Copy Link
Copy Source

@btbxbob commented on GitHub (Feb 8, 2025):

the same here, it occurs when create dataset in /datasets/create, selecting "from website"

@btbxbob commented on GitHub (Feb 8, 2025): the same here, it occurs when create dataset in /datasets/create, selecting "from website"
yindo commented 2026-02-21 18:23:00 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @conflock. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • Reported issues with Firecrawl and Jina Reader APIs in Dify version 0.15.2 when self-hosted via Docker.
  • Encountering a "Bad Request" error with status code 400.
  • Suggested checks include verifying parameters, provider, API key configuration, and endpoint accuracy.
  • @btbxbob confirmed the same issue when creating a dataset from a website, indicating a broader problem.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify. If so, you can keep the discussion open by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Mar 15, 2025): Hi, @conflock. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - Reported issues with Firecrawl and Jina Reader APIs in Dify version 0.15.2 when self-hosted via Docker. - Encountering a "Bad Request" error with status code 400. - Suggested checks include verifying parameters, provider, API key configuration, and endpoint accuracy. - @btbxbob confirmed the same issue when creating a dataset from a website, indicating a broader problem. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of Dify. If so, you can keep the discussion open by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 stale 🐞 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#7911
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?