starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-25 08:46:00 +03:00

[GH-ISSUE #1232] 404 error on all play requests on Koel v4.4.0 #700

New issue

Closed

opened 2026-02-26 02:34:00 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 02:34:00 +03:00

Owner

Originally created by @Hyzual on GitHub (Jun 11, 2020).
Original GitHub issue: https://github.com/koel/koel/issues/1232

Describe the bug
I cannot play any song from my library. When I inspect the network with dev tools, I see that all requests like https://<my-koel-domain>/api/<song-id>/play result in 404 error.
I could not find any logs that would explain what the problem is.
I just upgraded to Koel v4.4.0 (from v.4.3.0) and my library played fine before so I can only guess there is a configuration change needed somewhere ??

To reproduce
Steps to reproduce the behavior:

Upgrade from v4.3.0
Play any song from your library
The song is "loading indefinitely", network shows the /api/<song-id>/play request ends in 404 error.

Expected behavior
I expected the media to be loaded and my song to play.

Screenshots
I did not add a screen shot, please let me know if they're needed.

Environment

Koel version v4.4.0
OS: Linux Debian Buster in a Docker container
Browser: Firefox 77.0.1
PHP version: PHP 7.3.15
Node version: node 12

Additional context
Not sure what is needed. Maybe it's due to my context but I don't know where to look.

Originally created by @Hyzual on GitHub (Jun 11, 2020). Original GitHub issue: https://github.com/koel/koel/issues/1232 **Describe the bug** I cannot play any song from my library. When I inspect the network with dev tools, I see that all requests like `https://<my-koel-domain>/api/<song-id>/play` result in 404 error. I could not find any logs that would explain what the problem is. I just upgraded to Koel v4.4.0 (from v.4.3.0) and my library played fine before so I can only guess there is a configuration change needed somewhere ?? **To reproduce** Steps to reproduce the behavior: 1. Upgrade from v4.3.0 2. Play any song from your library 3. The song is "loading indefinitely", network shows the `/api/<song-id>/play` request ends in 404 error. **Expected behavior** I expected the media to be loaded and my song to play. **Screenshots** I did not add a screen shot, please let me know if they're needed. **Environment** - Koel version v4.4.0 - OS: Linux Debian Buster in a Docker container - Browser: Firefox 77.0.1 - PHP version: PHP 7.3.15 - Node version: node 12 **Additional context** Not sure what is needed. Maybe it's due to my context but I don't know where to look.

kerem closed this issue

2026-02-26 02:34:00 +03:00

kerem commented

2026-02-26 02:34:00 +03:00

Author

Owner

@Hyzual commented on GitHub (Jun 11, 2020):

~~I just downgraded to v4.3.0 and the same songs play fine, no 404 whatsoever.~~
Maybe I've missed some configuration change, I did not see anything mentioned in the release 😕

@Hyzual commented on GitHub (Jun 11, 2020): ~~I just downgraded to v4.3.0 and the same songs play fine, no 404 whatsoever.~~ Maybe I've missed some configuration change, I did not see anything mentioned in the release :confused:

kerem commented

2026-02-26 02:34:01 +03:00

Author

Owner

@Hyzual commented on GitHub (Jun 11, 2020):

Scratch that, I'm also reproducing with v4.3.0. I'm investigating, it's likely a problem on my end.

@Hyzual commented on GitHub (Jun 11, 2020): Scratch that, I'm also reproducing with v4.3.0. I'm investigating, it's likely a problem on my end.

kerem commented

2026-02-26 02:34:01 +03:00

Author

Owner

@Hyzual commented on GitHub (Jun 11, 2020):

Ok I've identified the issue. My volume containing my music library is /media. In the dockerfile I changed the default from /media to /music because /media is reserved in the Filesystem Hierarchy Standard for mounting usb drives and cd-roms and it seemed neater to use something else.

Since koel derives the song ids in part from the path of the song in the filesystem, I cannot change my volume to /music. Mounting everything to /music essentially has the same result as dropping my database with all the playlists, favorites, etc. being erased because the song ids would all change. So I kept everything at /media and I forgot that during my personal upgrade process I need to edit the apache configuration to point there instead of /music.
By the way https://github.com/koel/koel/issues/36#issue-122109241 helped me figure out what was happening.

Anyway, I'll close this. Sorry for the noise, v4.4.0 works great :).

@Hyzual commented on GitHub (Jun 11, 2020): Ok I've identified the issue. My volume containing my music library is `/media`. In the dockerfile I changed the default from `/media` to `/music` because `/media` is reserved in the [Filesystem Hierarchy Standard](https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) for mounting usb drives and cd-roms and it seemed neater to use something else. Since koel derives the song ids in part from the path of the song in the filesystem, I cannot change my volume to `/music`. Mounting everything to `/music` essentially has the same result as dropping my database with all the playlists, favorites, etc. being erased because the song ids would all change. So I kept everything at `/media` and I forgot that during my personal upgrade process I need to edit the apache configuration to point there instead of `/music`. By the way https://github.com/koel/koel/issues/36#issue-122109241 helped me figure out what was happening. Anyway, I'll close this. Sorry for the noise, v4.4.0 works great :).

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/koel-koel#700

No description provided.

Rows
Columns