[GH-ISSUE #239] Error 500 when playing a song #176

Closed
opened 2026-02-26 02:32:21 +03:00 by kerem · 1 comment
Owner

Originally created by @drazik on GitHub (Feb 17, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/239

Hello,

I have a strange issue when I want to play a song. The following URL is requested but returns a HTTP 500 error :

http://my.superb.host/api/db18d9ad4d44124eb0f018072e2454c0/play?jwt-token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOjEsImlzcyI6Imh0dHA6XC9cL2tvZWwuamVzbW9kcmF6aWsuZnJcL2FwaVwvbWUiLCJpYXQiOjE0NTU3Mzc1MjQsImV4cCI6MTQ1NjM0MjMyNCwibmJmIjoxNDU1NzM3NTI0LCJqdGkiOiJmMDc0NjA4NzlmZWJiMDNlN2NkYjBkZTYyMTgyY2ZkMCJ9.z1nCpKdSKs_bWjgXt0IkDInG9rJq6Mmcs6MEG-MeBA8

What is really strange is that this error only happens when reaching koel via apache2. When I run php artisan serve --host 0.0.0.0, there is no problem and the song is playing.

The only difference I see is the token :

http://192.168.1.141:8000/api/db18d9ad4d44124eb0f018072e2454c0/play?jwt-token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOjEsImlzcyI6Imh0dHA6XC9cLzE5Mi4xNjguMS4xNDE6ODAwMFwvYXBpXC9tZSIsImlhdCI6MTQ1NTY2MjQyMiwiZXhwIjoxNDU2MjY3MjIyLCJuYmYiOjE0NTU2NjI0MjIsImp0aSI6IjkxOWViODQ5YTcyMmY5NWM2NmEyN2NhZjg0N2VjMjZkIn0.BHono0EDo5JcHEcBgEhGcu8vOCAG_IU9QzHjVeon7d8

Still I don't think it makes any difference. So I looked in my apache error logs and absolutely nothing is related to this.

I put 777 rights on the koel folder and every files it contains, just in case, but I still get the error. I can't figure what is going on. Does somebody encountered the same issue and found a way to resolve it?

Thank you very much, for the work and the time spent on this project.

Originally created by @drazik on GitHub (Feb 17, 2016). Original GitHub issue: https://github.com/koel/koel/issues/239 Hello, I have a strange issue when I want to play a song. The following URL is requested but returns a HTTP 500 error : ``` http://my.superb.host/api/db18d9ad4d44124eb0f018072e2454c0/play?jwt-token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOjEsImlzcyI6Imh0dHA6XC9cL2tvZWwuamVzbW9kcmF6aWsuZnJcL2FwaVwvbWUiLCJpYXQiOjE0NTU3Mzc1MjQsImV4cCI6MTQ1NjM0MjMyNCwibmJmIjoxNDU1NzM3NTI0LCJqdGkiOiJmMDc0NjA4NzlmZWJiMDNlN2NkYjBkZTYyMTgyY2ZkMCJ9.z1nCpKdSKs_bWjgXt0IkDInG9rJq6Mmcs6MEG-MeBA8 ``` What is really strange is that this error only happens when reaching koel via apache2. When I run `php artisan serve --host 0.0.0.0`, there is no problem and the song is playing. The only difference I see is the token : ``` http://192.168.1.141:8000/api/db18d9ad4d44124eb0f018072e2454c0/play?jwt-token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOjEsImlzcyI6Imh0dHA6XC9cLzE5Mi4xNjguMS4xNDE6ODAwMFwvYXBpXC9tZSIsImlhdCI6MTQ1NTY2MjQyMiwiZXhwIjoxNDU2MjY3MjIyLCJuYmYiOjE0NTU2NjI0MjIsImp0aSI6IjkxOWViODQ5YTcyMmY5NWM2NmEyN2NhZjg0N2VjMjZkIn0.BHono0EDo5JcHEcBgEhGcu8vOCAG_IU9QzHjVeon7d8 ``` Still I don't think it makes any difference. So I looked in my apache error logs and absolutely nothing is related to this. I put 777 rights on the koel folder and every files it contains, just in case, but I still get the error. I can't figure what is going on. Does somebody encountered the same issue and found a way to resolve it? Thank you very much, for the work and the time spent on this project.
kerem closed this issue 2026-02-26 02:32:21 +03:00
Author
Owner

@drazik commented on GitHub (Feb 17, 2016):

Ok closing this one. I found the existence of the storage/logs/laravel.log file, which showed me that this is a permission problem. When running php artisan serve, the songs are read by my user, who has the right permissions. But apache didn't have the right permissions.

Thanks.

<!-- gh-comment-id:185398059 --> @drazik commented on GitHub (Feb 17, 2016): Ok closing this one. I found the existence of the `storage/logs/laravel.log` file, which showed me that this is a permission problem. When running `php artisan serve`, the songs are read by my user, who has the right permissions. But apache didn't have the right permissions. Thanks.
Sign in to join this conversation.
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#176
No description provided.