-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Self-Host] Working with Dify #1082
Comments
ccing @ftonato |
Hey @soccken can you pull the latest Dify? It should be fixed now |
The version of dify I am using is 0.13.2 |
Hello, can you try to use the latest version (0.15.2) they have? |
I get different errors when trying to use 0.15.2 and the latest firecrawl with the docker_compose in the repo. I noticed the v0 endpoint works, but the v1 doesn't when manually testing that. See my comments in in #713 |
Hey @rothnic, |
It worked with the 0.13.2 version |
My issue seemed to be related to something in firecrawl because after I resolved the issue in this pr #1131, v0.15.2 now works and the v1 endpoints now work (via curl), which they didn't before. |
As it seems that this problem is no longer occurring, I am going to close the issue. Thanks for the notes/contributions, and if there is still a problem, please open a new issue related to this one |
We are currently thinking of connecting Dify and Firecrawl.
The current environment is built on Amazon's AWS with a server for Dify and a server for Firecrawl. In addition, we have built the server for Dify and Firecrawl on each server with the docker compose command.
When connecting to Firecrawl from within the Dify web application, I get the following error
HTTPConnectionPool retries exceeded with url: /v0/crawl (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at ... >:Failed to establish a new connection: [Errono 111] Connection refused'))
What is the solution for this situation?
The text was updated successfully, but these errors were encountered: