[GH-ISSUE #926] Play() Failed to load resource: the server responded with a status of 500 - S3 #600

Closed
opened 2026-02-26 02:33:40 +03:00 by kerem · 2 comments
Owner

Originally created by @djevo1 on GitHub (Mar 1, 2019).
Original GitHub issue: https://github.com/koel/koel/issues/926

Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue:

  • [ X] You have read and followed closely the Wiki, Upgrade Guide, as well as Troubleshooting
  • [X ] The issue has not been reported before
  • [X ] This is not a "how to install on Windows" or "why is my npm messed up" question
  • [X ] You're a cool person

All checked? Now also make sure your issue

This is in regards to the current release. I have setup koel with AWS and lambda and as songs are added to the bucket koels database is also updated. However, when I go to play the song I get this error

Play() Failed to load resource: the server responded with a status of 500

I am running through nginx and php-fpm and have combed through the logs but have no server-side errors to report. I have the S3readonly permission setup with the IAM key given to koel so I unsure where the issue is coming from. I have also tried adding full permissions but there is no change.

Originally created by @djevo1 on GitHub (Mar 1, 2019). Original GitHub issue: https://github.com/koel/koel/issues/926 Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue: - [ X] You have read and followed closely the [Wiki](https://koel.phanan.net/docs), [Upgrade Guide](https://github.com/phanan/koel/releases), as well as [Troubleshooting](https://koel.phanan.net/docs/#/troubleshooting) - [X ] The issue has not been reported before - [X ] This is not a "how to install on Windows" or "why is my npm messed up" question - [X ] You're a cool person All checked? Now also make sure your issue This is in regards to the current release. I have setup koel with AWS and lambda and as songs are added to the bucket koels database is also updated. However, when I go to play the song I get this error Play() Failed to load resource: the server responded with a status of 500 I am running through nginx and php-fpm and have combed through the logs but have no server-side errors to report. I have the S3readonly permission setup with the IAM key given to koel so I unsure where the issue is coming from. I have also tried adding full permissions but there is no change.
Author
Owner

@BrookeDot commented on GitHub (Apr 22, 2020):

Hi @djevo1 can you confirm if this is still happening with the latest version of Koel? If so, can you provide more details? It sounds like perhaps AWS is responding with a 500 but not enough details.

<!-- gh-comment-id:617551148 --> @BrookeDot commented on GitHub (Apr 22, 2020): Hi @djevo1 can you confirm if this is still happening with the latest version of Koel? If so, can you provide more details? It sounds like perhaps AWS is responding with a 500 but not enough details.
Author
Owner

@BrookeDot commented on GitHub (Jan 10, 2021):

I'll go ahead and close this out, but feel free to re-open if you are still having trouble.

<!-- gh-comment-id:757516694 --> @BrookeDot commented on GitHub (Jan 10, 2021): I'll go ahead and close this out, but feel free to re-open if you are still having trouble.
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#600
No description provided.