[GH-ISSUE #901] Can't use anymore after last upgrade #409

New issue

Closed

opened 2026-02-25 23:34:10 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 23:34:10 +03:00

Owner

Originally created by @edied2002 on GitHub (May 4, 2024).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/901

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.

Originally created by @edied2002 on GitHub (May 4, 2024). Original GitHub issue: https://github.com/go-shiori/shiori/issues/901 ## 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.

kerem

2026-02-25 23:34:10 +03:00

closed this issue
added the
type:bug
label

kerem commented

2026-02-25 23:34:10 +03:00

Author

Owner

@fmartingr commented on GitHub (May 5, 2024):

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?

@fmartingr commented on GitHub (May 5, 2024): 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?

kerem commented

2026-02-25 23:34:10 +03:00

Author

Owner

@edied2002 commented on GitHub (May 5, 2024):

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: https://github.com/go-shiori/shiori/issues/546

@edied2002 commented on GitHub (May 5, 2024): > 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: https://github.com/go-shiori/shiori/issues/546

kerem referenced this issue

2026-02-25 23:34:49 +03:00

[PR #411] [MERGED] fix: url modification when query param is empty #587