mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #1716] something about FORCE_HTTPS #942
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#942
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 @rustle123 on GitHub (Oct 17, 2023).
Original GitHub issue: https://github.com/koel/koel/issues/1716
Describe the bug
Not sure if it's a bug. There are two methods to access Koel
I installed lastest koel by using docker, and with Nginx behind. What I want is accessing koel with both methods above. When I set
FORCE_HTTPS = trueandAPP_URL=https://koel.rustle.cc, I can visit the website with method 1 but not method 2; when I setFORCE_HTTPS = falseandAPP_URL=http://koel.rustle.cc, I can visit the website with method 2 but not method 1.So how can I access koel with both methods?
Thx
@phanan commented on GitHub (Dec 28, 2023):
I don't think this is a bug and you should always use method 1 if HTTPS is an option anyway.