Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firecrawl and Jina Reader APIs don't work #13081

Open
5 tasks done
flockton opened this issue Jan 27, 2025 · 1 comment
Open
5 tasks done

Firecrawl and Jina Reader APIs don't work #13081

flockton opened this issue Jan 27, 2025 · 1 comment
Labels
🐞 bug Something isn't working

Comments

@flockton
Copy link

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

@dosubot dosubot bot added the 🐞 bug Something isn't working label Jan 27, 2025
Copy link

dosubot bot commented 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant