mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #725] Reverse Proxy: Mixed Content Error #518
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#518
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 @Nebucatnetzer on GitHub (Mar 10, 2018).
Original GitHub issue: https://github.com/koel/koel/issues/725
I've installed Keol today and so far it works quite well in the local network.
I run all my VMs behind a reverse proxy which serves the domain with SSL.
With Koel however I'm not able to get it working. I get mixed content errors:
I've tried quite a few things to get it working but nothing really worked.
The most promising solution was this one here:
https://stackoverflow.com/questions/29912997/laravel-routes-behind-reverse-proxy
Which I put into routes/web.php however then I get the following error:
I know there have been other similar errors but none of them seem to have been resolved completely and I think it would be good if there's a place where a setup like this is at least somewhat documented.
@Nebucatnetzer commented on GitHub (Mar 10, 2018):
I tried to setup the TrustedProxy package for Laravel but didn't succed with that either. Unfortunately I can't run it without SSL because I have setup transport security on the main domain.
@decaby7e commented on GitHub (Nov 21, 2018):
Same issue here while using it behind a Nginx reverse proxy. However, I run my web services behind Docker containers, which is essentially the same here.
@baumschubser commented on GitHub (Dec 3, 2018):
I tried a lot and then this worked for me (koel 3.7.2):
composer require shin1x1/laravel-force-https-url-schemeapp/Http/Kernel.phpadd the following line as line 31:'Shin1x1\ForceHttpsUrlScheme\ForceHttpsUrlScheme',The code will look like this:
This solution relies on this package.
@Redsandro commented on GitHub (Feb 18, 2019):
The solution by @baumschubser works for me. Except the
requirecommand hangs.I had to:
composer require shin1x1/laravel-force-https-url-scheme^C(Ctrl + C)composer updatecomposer install'Shin1x1\ForceHttpsUrlScheme\ForceHttpsUrlScheme'toKernel.phpThe problem is, everything is undone when
watchtowerdownloads a new docker container.It would be much appreciated if @phanan could implement functionality that allows running the koel container (e.g. above fix configurable) behind a proxy container, as this is increasingly common.
@Redsandro commented on GitHub (Feb 20, 2019):
Something for people who are getting bored from doing this every time again:
Note: Replace
--userwith your own values.@nebulade commented on GitHub (Apr 1, 2019):
I am looking into packaging koel for Cloudron and hit the same issue. As far as I understand the env file, shouldn't those URLs be generated from the
APP_URLvariable?@mbreedlove commented on GitHub (Oct 28, 2019):
I agree with @nebulade, URLs should be generated from
APP_URL, however, changingAPP_URLseems to have no effect.@BrookeDot commented on GitHub (Apr 23, 2020):
I'm closing this as the initial issue has seemed to be resolved. If
APP_URLstill is not behaving as expected please open a new issue to address that.@sugartarou commented on GitHub (Dec 30, 2023):
What is the solution for latest(6.11.5) ?
I tried above solution, but not worked.
@sugartarou commented on GitHub (Dec 30, 2023):
Sorry, I found the solution for this.
I set FORCE_HTTPS=true in .env.