mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #2095] [Bug] 500 Internal Server Error on Koel Homepage #1093
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#1093
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 @sayem314 on GitHub (Sep 11, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/2095
Upon running the docker-compose.yml file, the Koel service fails to load the homepage and displays a "500 Internal Server Error" message. The Koel container logs show a PHP fatal error related to "headers already sent," which is often a symptom of an underlying application issue. The root cause, as seen in the PostgreSQL database container logs, is a series of
relation "personal_access_tokens" does not existerrors. This indicates that the database schema required by Koel has not been created, preventing the application from functioning correctly.@phanan commented on GitHub (Sep 12, 2025):
Please follow the issue template.