mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #1284] SQLSTATE[HY000]: General error: 8 attempt to write a readonly database #737
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#737
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Feb 24, 2021).
Original GitHub issue: https://github.com/koel/koel/issues/1284
Describe the bug
When I change the artist name / song name / album or any other metadata via the webinterface and I click "Update", the dialog disappears, the processing animation appears but then the dialog pops up again and the information is left unchanged.
When inspecting with the browser console, it reveals the following error:
And the nginx reverse proxy logs this request: (I have the nginx configuration recommended by Laravel with some additions from the example)
To reproduce
Steps to reproduce the behavior:
Expected behavior
After the processing animation the dialog disappears and the information is changed.
Environment
I'll be happy to provide any additional infos!
@ghost commented on GitHub (Feb 25, 2021):
I'm quite sure now after some testing that it has to do with the passing of the nginx proxy, because hosting with
php artisan serveworks.I'll close, since it's outside the scope of this repo but I will keep this issue updated when I find the solution, for others.
@ghost commented on GitHub (Feb 26, 2021):
Solved it. Turned out to be the same as #1280. (See this reply)