Replies: 3 comments 1 reply
-
Has it been resolved |
Beta Was this translation helpful? Give feedback.
-
when I use got an error on the console
|
Beta Was this translation helpful? Give feedback.
-
After upgrading Dify from 1.4.1 to 1.5.1, I encountered the same issue. I noticed that the docker-plugin_daemon-1 container kept restarting, reporting error that S3_USE_AWS was empty, whereas a boolean value is expected. The problem is likely the absence of the PLUGIN_S3_USE_AWS variable in the .env file (when upgrading from an older version), and the default value of S3_USE_AWS in docker-compose.yaml is empty instead of "false". The fix is to add PLUGIN_S3_USE_AWS=false to the .env file. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Self Checks
Dify version
1.4.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
I followed the instructions in the ReadMe exactly, using the Docker deployment.
My platform is Ubuntu 22.04,on Jetson Orin NX 16G
It's work in the same step when i do this on my own computer with Exactly same steps,
but when I try it on my Jetson Orin,it failed.
I configured the Docker Daemon with the clash vpn on Jetson Orin, and I don't know if this will make a difference
I have tried to close my vpn,but it also doesn't work、
✔️ Expected Behavior
no error alert
❌ Actual Behavior
I can browse“Model market”, but I can't install them and report errors
if I copy this link and visit it on my browser, I can download this model, so I am sure my internet is connected
Beta Was this translation helpful? Give feedback.
All reactions