langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Version 0.15.3、Connect to ragflow external knowledge base error, 403 #8727

New Issue
Closed
opened 2026-02-21 18:27:15 -05:00 by yindo · 11 comments
yindo commented 2026-02-21 18:27:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @Mamba082481 on GitHub (Feb 27, 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 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

Version 0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I confirm that my configuration is correct.

dify error:
Image

ragflow error:

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @Mamba082481 on GitHub (Feb 27, 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 [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 Version 0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I confirm that my configuration is correct. dify error: ![Image](https://github.com/user-attachments/assets/db30c6e1-04a6-4de5-8aca-f8e0fbb157ff) ragflow error: ![Image](https://github.com/user-attachments/assets/868385e1-6455-4134-a116-75d0f9368f4d) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug👻 feat:rag labels 2026-02-21 18:27:15 -05:00
yindo closed this issue 2026-02-21 18:27:15 -05:00
yindo commented 2026-02-21 18:27:15 -05:00
Author
Owner
Copy Link
Copy Source

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

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

I found a similar closed issue that might help with your 403 Forbidden error when connecting to the ragflow external knowledge base using Dify version 0.15.3 on a self-hosted Docker setup. The suggested solution involves modifying the Squid ACL configuration file at /dify/docker/ssrf_proxy/squid.conf.template with the following configuration:

http_access allow Safe_ports
http_access allow CONNECT SSL_ports
http_access allow localhost manager
http_access deny manager
http_access allow localhost
include /etc/squid/conf.d/*.conf
http_access deny all

Additionally, ensure that port 175 is allowed in the configuration, as this is the port used by the API endpoint. After making these changes, restart the SSRF proxy container and your Docker compose setup to apply the new configuration. If the issue persists, double-check the API endpoint and key configuration, and ensure they are correctly set up in your Dify environment [1].

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 27, 2025): <!-- Greeting --> @Mamba082481 Hello there! I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. Let's work together to solve this issue. <!-- Answer --> I found a similar closed issue that might help with your 403 Forbidden error when connecting to the ragflow external knowledge base using Dify version 0.15.3 on a self-hosted Docker setup. The suggested solution involves modifying the Squid ACL configuration file at `/dify/docker/ssrf_proxy/squid.conf.template` with the following configuration: ```plaintext http_access allow Safe_ports http_access allow CONNECT SSL_ports http_access allow localhost manager http_access deny manager http_access allow localhost include /etc/squid/conf.d/*.conf http_access deny all ``` Additionally, ensure that port 175 is allowed in the configuration, as this is the port used by the API endpoint. After making these changes, restart the SSRF proxy container and your Docker compose setup to apply the new configuration. If the issue persists, double-check the API endpoint and key configuration, and ensure they are correctly set up in your Dify environment <sup>[[1]](https://github.com/langgenius/dify/issues/13993)</sup>. <!-- 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/8e795f48-b52d-4cd0-8770-a5ce6f1517a0?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/8e795f48-b52d-4cd0-8770-a5ce6f1517a0?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/8e795f48-b52d-4cd0-8770-a5ce6f1517a0?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/8e795f48-b52d-4cd0-8770-a5ce6f1517a0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8e795f48-b52d-4cd0-8770-a5ce6f1517a0?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/8e795f48-b52d-4cd0-8770-a5ce6f1517a0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8e795f48-b52d-4cd0-8770-a5ce6f1517a0?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:15 -05:00
Author
Owner
Copy Link
Copy Source

@quchenchen commented on GitHub (Feb 28, 2025):

This issue has nothing to do with dify. It is recommended to raise an issue on ragflow. Since version 0.15.0, dify has upgraded its components, but the ragflow SDK has not been updated accordingly.

@quchenchen commented on GitHub (Feb 28, 2025): This issue has nothing to do with dify. It is recommended to raise an issue on ragflow. Since version 0.15.0, dify has upgraded its components, but the ragflow SDK has not been updated accordingly.
yindo commented 2026-02-21 18:27:15 -05:00
Author
Owner
Copy Link
Copy Source

@Mamba082481 commented on GitHub (Feb 28, 2025):

This issue has nothing to do with dify. It is recommended to raise an issue on ragflow. Since version 0.15.0, dify has upgraded its components, but the ragflow SDK has not been updated accordingly.

已解决，是 dify 的问题

@Mamba082481 commented on GitHub (Feb 28, 2025): > This issue has nothing to do with dify. It is recommended to raise an issue on ragflow. Since version 0.15.0, dify has upgraded its components, but the ragflow SDK has not been updated accordingly. 已解决，是 dify 的问题
yindo commented 2026-02-21 18:27:15 -05:00
Author
Owner
Copy Link
Copy Source

@simpleobj commented on GitHub (Feb 28, 2025):

This issue has nothing to do with dify. It is recommended to raise an issue on ragflow. Since version 0.15.0, dify has upgraded its components, but the ragflow SDK has not been updated accordingly.

已解决，是 dify 的问题

怎么解决的，help me

@simpleobj commented on GitHub (Feb 28, 2025): > > This issue has nothing to do with dify. It is recommended to raise an issue on ragflow. Since version 0.15.0, dify has upgraded its components, but the ragflow SDK has not been updated accordingly. > > 已解决，是 dify 的问题 怎么解决的，help me
yindo commented 2026-02-21 18:27:15 -05:00
Author
Owner
Copy Link
Copy Source

@GlocKieHuan commented on GitHub (Mar 13, 2025):

I also encountered this problem. Please share how you solved it. Thank you. @Mamba082481

@GlocKieHuan commented on GitHub (Mar 13, 2025): I also encountered this problem. Please share how you solved it. Thank you. @Mamba082481
yindo commented 2026-02-21 18:27:15 -05:00
Author
Owner
Copy Link
Copy Source

@asking002 commented on GitHub (Mar 18, 2025):

@Mamba082481 求助，我系统重装了，新版本的dify也遇到这个问题，之前是好的。
http_access allow Safe_ports
http_access allow CONNECT SSL_ports
http_access allow localhost manager
http_access deny manager
http_access allow localhost
include /etc/squid/conf.d/*.conf
http_access deny all 尝试更改后也没有效果

@asking002 commented on GitHub (Mar 18, 2025): @Mamba082481 求助，我系统重装了，新版本的dify也遇到这个问题，之前是好的。 http_access allow Safe_ports http_access allow CONNECT SSL_ports http_access allow localhost manager http_access deny manager http_access allow localhost include /etc/squid/conf.d/*.conf http_access deny all 尝试更改后也没有效果
yindo commented 2026-02-21 18:27:16 -05:00
Author
Owner
Copy Link
Copy Source

@Yue-Lyu123 commented on GitHub (Mar 19, 2025):

I also encountered the same issue in Dify version 0.15.3 and Ragflow version 0.17.2, where Ragflow reported a 403 error. I found that my Ragflow API key had been updated, but when I copied and pasted it into Dify's external knowledge base, it didn't work. So, I deleted the "External Knowledge Base API" and after re-adding it, it worked.

@Yue-Lyu123 commented on GitHub (Mar 19, 2025): I also encountered the same issue in Dify version 0.15.3 and Ragflow version 0.17.2, where Ragflow reported a 403 error. I found that my Ragflow API key had been updated, but when I copied and pasted it into Dify's external knowledge base, it didn't work. So, I deleted the "External Knowledge Base API" and after re-adding it, it worked.
yindo commented 2026-02-21 18:27:16 -05:00
Author
Owner
Copy Link
Copy Source

@asking002 commented on GitHub (Mar 21, 2025):

@Yue-Lyu123 it works，thanks

@asking002 commented on GitHub (Mar 21, 2025): @Yue-Lyu123 it works，thanks
yindo commented 2026-02-21 18:27:16 -05:00
Author
Owner
Copy Link
Copy Source

@IAOTW commented on GitHub (Apr 3, 2025):

@Yue-Lyu123 ,same issue in Dify version 0.15.3 and Ragflow version 0.17.2, thanks

@IAOTW commented on GitHub (Apr 3, 2025): @Yue-Lyu123 ,same issue in Dify version 0.15.3 and Ragflow version 0.17.2, thanks
yindo commented 2026-02-21 18:27:16 -05:00
Author
Owner
Copy Link
Copy Source

@Be11amy commented on GitHub (May 16, 2025):

请问是怎么解决的？

@Be11amy commented on GitHub (May 16, 2025): 请问是怎么解决的？
yindo commented 2026-02-21 18:27:16 -05:00
Author
Owner
Copy Link
Copy Source

@GlocKieHuan commented on GitHub (May 16, 2025):

你好呀，这里是GH的邮件自动回复，你的邮件我已经收到啦，祝好~~~

@GlocKieHuan commented on GitHub (May 16, 2025): 你好呀，这里是GH的邮件自动回复，你的邮件我已经收到啦，祝好~~~
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 🐞 bug 👻 feat:rag
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#8727
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?