-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
arm sandbox and squid error #14335
Comments
I found a similar unsolved discussion regarding sandbox issues in the Dify repository: sandbox can't use [1]. For the issues you're encountering:
For Squid configuration, you can refer to the recommended settings for permissions and IPv6 in a Dify setup [2]. 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 |
I am using the Squid configuration of dify, which is the default configuration and has not been changed @dosu |
The default Squid configuration in Dify might not explicitly allow all necessary IPv6 traffic and could have restrictive access controls, leading to errors. To address these issues:
For more detailed configurations, you can edit the 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 |
It's no use, can you help me take a look? Squid cannot run, causing the page to be inaccessible now. @crazywoola |
Self Checks
Dify version
0.15.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
In the ARM environment, Sandbox and Ubuntu/Squit encounter errors, and the error persists after restarting repeatedly
✔️ Expected Behavior
fix error
❌ Actual Behavior
error
The text was updated successfully, but these errors were encountered: