-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fail to upgrade to 0.6.12 #5730
Comments
Hey @paulcx! 👋 I'm here to assist you with any bugs, questions, or contributions while you wait for a human maintainer. Let's work together to resolve any issues you're encountering. To resolve the
Ensure that the Additionally, check the redis:
image: redis:6-alpine
restart: always
volumes:
- ./volumes/redis/data:/data
command: redis-server --requirepass ${REDIS_PASSWORD:-difyai123456}
healthcheck:
test: [ "CMD", "redis-cli", "ping" ]
# uncomment to expose redis port to host
# ports:
# - "6379:6379" Make sure the |
does it related to env file? i used the default env file middleware.env |
Yes, the issue could be related to the REDIS_HOST=redis
REDIS_PORT=6379
REDIS_PASSWORD=difyai123456
REDIS_DB=0
REDIS_USERNAME=
REDIS_USE_SSL=false These settings should match the Redis service configuration in your services:
# The redis cache.
redis:
image: redis:6-alpine
restart: always
volumes:
# Mount the redis data directory to the container.
- ./volumes/redis/data:/data
# Set the redis password when startup redis server.
command: redis-server --requirepass ${REDIS_PASSWORD:-difyai123456}
ports:
- "6379:6379" Make sure to replace docker compose down
docker compose up -d Then, verify that all containers, including Redis, are running: docker compose ps |
what is the difference of use between docker-compose.middleware.yaml and docker-compose.yaml? which one should be used to upgrade? Actually, redis server works fine but somehow worker can connect redis server. it should be something wrong with the config? |
The differences between For upgrading, you can use either Since your Redis server works fine but the worker cannot connect to it, double-check the following:
By ensuring these configurations are correct, you should be able to resolve the connection issue between the worker and the Redis server. |
also have similar issue - docker @ windows run with @echo off then output bunch of warnings
(...) |
using default env file warning gone but now 2024-06-28 22:30:39 ssrf_proxy-1 | sh: 1: /docker-entrypoint.sh: not found and 2024-06-28 22:30:46 nginx-1 | sh: 1: /docker-entrypoint.sh: not found 2 volumes are created but are 0 byte files |
I also could not start DIFY 0.6.12 with the following error.
I was able to start it successfully by using docker-legacy.
Since docker-legacy/volumes is the initial state, DIFY will start on the first signup screen. |
"docker\nginx\docker-entrypoint.sh" Converting these two files from CRLF to LF will resolve the issue. You can use "Notepad++". Open the file, go to Edit, EOL Conversion, select UNIX (LF), and save the file. I spent quite some time figuring this out, not sure if it counts as a bug? |
|
可以解决nginx,ssrf_proxy的docker无法启动问题 |
On windows, if git config core.autocrlf is true (default), the above problem occurs and DIFY cannot be started. You can manually edit file CRLF -> LF as described above, or changing the git config and pulling should solve the problem.
|
It works finally, great ! Thanks a lot ! |
all 0.6.12 containers are started but got this issue at (http://localhost/install) page ? |
I guess @MWang-TS you need to attach the screenshot of web console. |
The screenshot above is the interface for initializing the administrator user password ,after I click [Setting up an admin account] from signin page. |
+1 ❌ Actual Behavior |
Self Checks
Dify version
0.6.12
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Copy the docker/.env.example file to a new file named .env and customize it as needed.
Run docker compose up to start the services.
✔️ Expected Behavior
upgrade
❌ Actual Behavior
redis.exceptions.ConnectionError: Error 111 connecting to localhost:6379. Connection refused.
The text was updated successfully, but these errors were encountered: