-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
[Bug]: Upgrade 4.0.0-beta-364 completely broke setup - rollback not working #4218
Comments
Some mor} logs I found when checking coolifies container logs:
|
I found the docker-compose setup of coolify in |
Was able to re-run the upgrade script in |
Running the script worked for me as well. Thanks! |
Didn't break anything for me but upgrade got stuck with this in the logs:
|
Maybe you could try running a command like |
Had the same problem. Running the mentioned script Running under |
Same problem, going from 362 to 364, clicked Upgrade, now it's a permanent 500 Internal Error trying to access Coolify. This fixed it for me too: |
Error Message and Logs
I just pressed the upgrade button and suddenly received a 500 from the3 system. If I interpret the logs correctly there seems to be an issue with redis. Though I don't find a way to directly interact with coolifies stack.
When trying to rollback I receive an error because coolify tries to write the
/data/coolify
-directory. I don't want to delete this directory, because it looks like this is, where all my data is stored.What's the best way to move forward here?
Steps to Reproduce
/data/coolify
directoryExample Repository URL
No response
Coolify Version
v4.0.0-beta-364
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: