mirror of
https://github.com/koel/koel.git
synced 2026-04-26 09:15:59 +03:00
[GH-ISSUE #1959] [Bug]: Reverse proxy issue #1044
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#1044
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 @Fancham on GitHub (Jun 17, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/1959
Originally assigned to: @phanan on GitHub.
Read the Troubleshooting guide.
Reproduction steps
1.Web site Koel is up on HTTPS url without reverse proxy. I can connect and start songs.
2.Web site Koel is blanck on HTTPS url with the reverse proxy. I can't connect
3.On IOS app, I can connect and listen songs within the reverse proxy
Expected behavior
I can connect with reverse proxy url and start songs
Actual behavior
Web site Koel is blanck on HTTPS url with the reverse proxy. I can't connect
Logs
No response
Koel version
Last version
How did you install Koel?
Official Docker image
Additional information
@phanan commented on GitHub (Jun 17, 2025):
Based on your description, this 99% is due to the server not serving assets over SSL (you can verify via the browser's console). Once you solve that problem, everything should work.
@Fancham commented on GitHub (Jun 17, 2025):
Tanks for your reply Phanan. How I can fix this issue? I can see issue on assets indeed : Cross-Origin Request Blocking: The "Same Origin" policy does not allow viewing of the remote resource located on .../build/assets/*
Thanks for your hep!
Le 17 juin 2025 à 21:07, Phan An @.***> a écrit :
[https://avatars.githubusercontent.com/u/8056274?s=20&v=4]phanan left a comment (koel/koel#1959)https://github.com/koel/koel/issues/1959#issuecomment-2981536784
Based on your description, this 99% is due to the server not serving assets over SSL (you can verify via the browser's console). Once you solve that problem, everything should work.
—
Reply to this email directly, view it on GitHubhttps://github.com/koel/koel/issues/1959#issuecomment-2981536784, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABTRQ2DEKGZ5YCFY5KZRQWL3EBRNRAVCNFSM6AAAAAB7QZUMQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBRGUZTMNZYGQ.
You are receiving this because you authored the thread.Message ID: @.***>
@phanan commented on GitHub (Jun 17, 2025):
Can you paste your web server config?
On Tue, Jun 17, 2025 at 21:18 Fancham @.***> wrote:
@Fancham commented on GitHub (Jun 17, 2025):
Koel is on a Synology’s NAS. I h’ave just set HTTPS port and HSTS is enable in web app. The only file I have is the apache config of the dockers’s container but it’s that of Koel’s docker. I didn't change it.
Le 17 juin 2025 à 21:31, Phan An @.***> a écrit :
[https://avatars.githubusercontent.com/u/8056274?s=20&v=4]phanan left a comment (koel/koel#1959)https://github.com/koel/koel/issues/1959#issuecomment-2981626125
Can you paste your web server config?
On Tue, Jun 17, 2025 at 21:18 Fancham @.***> wrote:
—
Reply to this email directly, view it on GitHubhttps://github.com/koel/koel/issues/1959#issuecomment-2981626125, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABTRQ2AI27NK2ODUJ7U4RYT3EBUKFAVCNFSM6AAAAAB7QZUMQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBRGYZDMMJSGU.
You are receiving this because you authored the thread.Message ID: @.***>
@phanan commented on GitHub (Jun 17, 2025):
I'm not familiar with Synology, so I can't give you a specific guide, but
basically you want the reverse proxy (nginx?) to be able to serve static
files via HTTPS. I think ChatGPT should be very useful here :)
Am Di., 17. Juni 2025 um 22:12 Uhr schrieb Fancham @.***
@Fancham commented on GitHub (Jun 17, 2025):
As I can see, I can add header on reverse proxy. Actually, I have Upgrade=$http_upgrade; Connection=$connection_upgrade.
Maybe, I have to add other param in header?
Le 17 juin 2025 à 21:31, Phan An @.***> a écrit :
[https://avatars.githubusercontent.com/u/8056274?s=20&v=4]phanan left a comment (koel/koel#1959)https://github.com/koel/koel/issues/1959#issuecomment-2981626125
Can you paste your web server config?
On Tue, Jun 17, 2025 at 21:18 Fancham @.***> wrote:
—
Reply to this email directly, view it on GitHubhttps://github.com/koel/koel/issues/1959#issuecomment-2981626125, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABTRQ2AI27NK2ODUJ7U4RYT3EBUKFAVCNFSM6AAAAAB7QZUMQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBRGYZDMMJSGU.
You are receiving this because you authored the thread.Message ID: @.***>
@Fancham commented on GitHub (Jun 18, 2025):
Hi Phanan,
As I can see, on Synology, reverse Proxy is managed by nginx. I can add header on reverse proxy. Actually, I have this settings :
Upgrade=$http_upgrade
Connection=$connection_upgrade
I don’t know how update config to make Koel works behind reverse proxy.
Thanks for your help.
Fancham
Le 17 juin 2025 à 22:16, Phan An @.***> a écrit :
[https://avatars.githubusercontent.com/u/8056274?s=20&v=4]phanan left a comment (koel/koel#1959)https://github.com/koel/koel/issues/1959#issuecomment-2981711159
I'm not familiar with Synology, so I can't give you a specific guide, but
basically you want the reverse proxy (nginx?) to be able to serve static
files via HTTPS. I think ChatGPT should be very useful here :)
Am Di., 17. Juni 2025 um 22:12 Uhr schrieb Fancham @.***
—
Reply to this email directly, view it on GitHubhttps://github.com/koel/koel/issues/1959#issuecomment-2981711159, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABTRQ2HFMEGPP5MWWJBNYKL3EBZRVAVCNFSM6AAAAAB7QZUMQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBRG4YTCMJVHE.
You are receiving this because you authored the thread.Message ID: @.***>
@phanan commented on GitHub (Jun 18, 2025):
Koel itself doesn't need any changes or configuration to work behind a
reverse proxy. This is most likely an issue/setup issue with the reverse
proxy itself, which I believe ChatGPT would be of great help if you prompt
properly (i.e. describing the setup, what happens etc.)
Am Mi., 18. Juni 2025 um 10:38 Uhr schrieb Fancham @.***