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

[Self-Host] Working with Dify #1082

Closed
soccken opened this issue Jan 21, 2025 · 9 comments
Closed

[Self-Host] Working with Dify #1082

soccken opened this issue Jan 21, 2025 · 9 comments
Assignees
Labels
bug Something isn't working self-host

Comments

@soccken
Copy link

soccken commented Jan 21, 2025

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?

@nickscamara
Copy link
Member

ccing @ftonato

@nickscamara nickscamara added the bug Something isn't working label Jan 25, 2025
@nickscamara
Copy link
Member

Hey @soccken can you pull the latest Dify? It should be fixed now

@soccken
Copy link
Author

soccken commented Jan 28, 2025

The version of dify I am using is 0.13.2

@ftonato
Copy link
Collaborator

ftonato commented Jan 28, 2025

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?

https://github.com/langgenius/dify/releases/tag/0.15.2

@rothnic
Copy link
Contributor

rothnic commented Feb 1, 2025

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

Copy link
Collaborator

ftonato commented Feb 3, 2025

Hey @rothnic,

We are aware of that problem. It was resolved with our last merge request to the repository five days ago. However, they haven’t created a release yet, so even when using v0.15.2, the issue is unfortunately still present.

langgenius/dify#13082

@soccken
Copy link
Author

soccken commented Feb 4, 2025

It worked with the 0.13.2 version

@rothnic
Copy link
Contributor

rothnic commented Feb 4, 2025

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.

@ftonato
Copy link
Collaborator

ftonato commented Feb 5, 2025

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

@ftonato ftonato closed this as completed Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working self-host
Projects
None yet
Development

No branches or pull requests

4 participants