Skip to content
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

Closed
edied2002 opened this issue May 4, 2024 · 2 comments
Closed

Can't use anymore after last upgrade #901

edied2002 opened this issue May 4, 2024 · 2 comments
Labels
type:bug Something isn't working

Comments

@edied2002
Copy link

Data

  • Shiori version: 1.6.4
  • Database Engine:default
  • Operating system: docker container
  • CLI/Web interface/Web Extension:

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.

@edied2002 edied2002 added the type:bug Something isn't working label May 4, 2024
@fmartingr
Copy link
Member

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?

@edied2002
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

2 participants