-
Notifications
You must be signed in to change notification settings - Fork 547
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
Can't use anymore after last upgrade #901
Comments
Hey @edied2002, did you solve this? It was caused by Shiori? From the logs you provide that's a change in the migration system for the next release. I upgraded my own instances without issues, from which version were you upgrading to that? |
Sorry, I searched and this was the problem as in this another post: #546 |
Data
Describe the bug / actual behavior
After last upgrade the web doesn't load and I can see this logs:
time="2024-05-04T14:22:32Z" level=warning msg="SHIORI_HTTP_SECRET_KEY is not set, using random value. This means that all sessions will be invalidated on server restart."
time="2024-05-04T14:22:32Z" level=fatal msg="Error running migration" error="failed to run migration from 0.0.0 to 0.1.0: failed to run transaction: failed to execute migration 0.0.0 to 0.1.0: attempt to write a readonly database (8)"
Expected behavior
Normal behavior
To Reproduce
Steps to reproduce the behavior:
I did nothing, just upgrade the container
Screenshots
If applicable, add screenshots to help explain your problem.
Notes
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: