langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

An error occurred in the plugin, please contact the author of langgenius/dify_extractor/dify_extractor for help, error type: ConnectError, error details: [Errno 111] Connection refused #695

New Issue
Closed
opened 2026-02-16 10:20:13 -05:00 by yindo · 8 comments
yindo commented 2026-02-16 10:20:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @Despairking on GitHub (Oct 9, 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 Dify issues & Dify Official Plugins, 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

1.9.1

Plugin version

Dify Extractor 0.0.5

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Error log

Image
Originally created by @Despairking on GitHub (Oct 9, 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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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 1.9.1 ### Plugin version Dify Extractor 0.0.5 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="924" height="410" alt="Image" src="https://github.com/user-attachments/assets/059f6d28-f6ca-42a5-806d-c16aa83d6746" /> ### ✔️ Error log <img width="924" height="410" alt="Image" src="https://github.com/user-attachments/assets/3aeae455-43a2-4712-9ff2-cb3c3a7c29f8" />
yindo added the bug label 2026-02-16 10:20:13 -05:00
yindo closed this issue 2026-02-16 10:20:13 -05:00
yindo commented 2026-02-16 10:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@tiagantos commented on GitHub (Oct 10, 2025):

What was the solution?

@tiagantos commented on GitHub (Oct 10, 2025): What was the solution?
yindo commented 2026-02-16 10:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@Despairking commented on GitHub (Oct 10, 2025):

What was the solution?

  1. Locate the Dify deployment directory, open the .env file, and modify the FILES_URL configuration according to your deployment method:
  1. Ensure that the 5001 port of the Dify API service is exposed externally and check the port mappings in the docker-compose.yaml file.
Image
@Despairking commented on GitHub (Oct 10, 2025): > What was the solution? 1. Locate the Dify deployment directory, open the .env file, and modify the FILES_URL configuration according to your deployment method: - Docker Compose deployment: set FILES_URL to http://api:5001 - Other deployment methods: set FILES_URL to http://Dify host IP:5001 2. Ensure that the 5001 port of the Dify API service is exposed externally and check the port mappings in the docker-compose.yaml file. <img width="560" height="135" alt="Image" src="https://github.com/user-attachments/assets/56cb22ef-ccc7-4f1c-8e59-9bcf3a22f66a" />
yindo commented 2026-02-16 10:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@tiagantos commented on GitHub (Oct 10, 2025):

What was the solution?

  1. Locate the Dify deployment directory, open the .env file, and modify the FILES_URL configuration according to your deployment method:
  1. Ensure that the 5001 port of the Dify API service is exposed externally.

How can I ensure that the 5001 port is exposed?

@tiagantos commented on GitHub (Oct 10, 2025): > > What was the solution? > > 1. Locate the Dify deployment directory, open the .env file, and modify the FILES_URL configuration according to your deployment method: > > * Docker Compose deployment: set FILES_URL to http://api:5001 > * Other deployment methods: set FILES_URL to http://:5001 > > 2. Ensure that the 5001 port of the Dify API service is exposed externally. How can I ensure that the 5001 port is exposed?
yindo commented 2026-02-16 10:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@Despairking commented on GitHub (Oct 10, 2025):

You can check the port mappings in the docker-compose.yaml file

@Despairking commented on GitHub (Oct 10, 2025): You can check the port mappings in the docker-compose.yaml file
yindo commented 2026-02-16 10:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@tiagantos commented on GitHub (Oct 10, 2025):

You can check the port mappings in the docker-compose.yaml file

Ok thank you for your help!

@tiagantos commented on GitHub (Oct 10, 2025): > You can check the port mappings in the docker-compose.yaml file Ok thank you for your help!
yindo commented 2026-02-16 10:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@boaty commented on GitHub (Oct 28, 2025):

What was the solution?

  1. Locate the Dify deployment directory, open the .env file, and modify the FILES_URL configuration according to your deployment method:
  1. Ensure that the 5001 port of the Dify API service is exposed externally.

i have the same issue when using pipeline for knowledge.
i deploy dify using docker compose and i set FILES_URL to http://api:5001. after restart the docker compose, everything dify website is extremly slow and unable to do anything.

then i switched to FILES_URL=http://Dify host IP:5001. Dify returned to normal state but error "An error occurred in the plugin, please contact the author of langgenius/dify_extractor/dify_extractor for help, error type: ConnectError, error details: [Errno 111] Connection refused" appear again.

please help

@boaty commented on GitHub (Oct 28, 2025): > > What was the solution? > > 1. Locate the Dify deployment directory, open the .env file, and modify the FILES_URL configuration according to your deployment method: > > * Docker Compose deployment: set FILES_URL to http://api:5001 > * Other deployment methods: set FILES_URL to http://Dify host IP:5001 > > 2. Ensure that the 5001 port of the Dify API service is exposed externally. i have the same issue when using pipeline for knowledge. i deploy dify using docker compose and i set FILES_URL to http://api:5001. after restart the docker compose, everything dify website is extremly slow and unable to do anything. then i switched to FILES_URL=http://Dify host IP:5001. Dify returned to normal state but error "An error occurred in the plugin, please contact the author of langgenius/dify_extractor/dify_extractor for help, error type: ConnectError, error details: [Errno 111] Connection refused" appear again. please help
yindo commented 2026-02-16 10:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@Despairking commented on GitHub (Oct 28, 2025):

Did you set the ports in your docker-compose.yaml file?

Image
@Despairking commented on GitHub (Oct 28, 2025): Did you set the ports in your docker-compose.yaml file? <img width="560" height="135" alt="Image" src="https://github.com/user-attachments/assets/a5513ed2-3361-49e6-80f2-ee2f27c390c2" />
yindo commented 2026-02-16 10:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@boaty commented on GitHub (Oct 29, 2025):

Did you set the ports in your docker-compose.yaml file?

Image

No, i did not. the docker-compose.yaml file kept the same as git pull sent.
So I added `ports: - "5001:5001", it works !!! but why?

Thank you

Best

@boaty commented on GitHub (Oct 29, 2025): > Did you set the ports in your docker-compose.yaml file? > > <img alt="Image" width="560" height="135" src="https://private-user-images.githubusercontent.com/70753774/506437511-a5513ed2-3361-49e6-80f2-ee2f27c390c2.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjE3OTQ5NjIsIm5iZiI6MTc2MTc5NDY2MiwicGF0aCI6Ii83MDc1Mzc3NC81MDY0Mzc1MTEtYTU1MTNlZDItMzM2MS00OWU2LTgwZjItZWUyZjI3YzM5MGMyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEwMzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMDMwVDAzMjQyMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRjMGU5ZTg4OTI4ZDEzZGMyMDU4NjVlMGY4Y2I1ZjIxYjQzOWE4NTUwYTlkYjIzM2JlNjMwZWExYThhOTk4MWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.KS5RKchW22QzOYreHPT02o0sgiE08Nvvh2Mujpe5bvY"> No, i did not. the docker-compose.yaml file kept the same as `git pull` sent. So I added `ports: - "5001:5001", it works !!! but why? Thank you Best
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label 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-official-plugins#695
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?