mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #360] https possible? #261
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#261
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 @anonaut on GitHub (Jun 17, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/360
im trying to run koel via https for various reasons. i tried to follow the installation guide and get the login interface, but when i want to log in nothing happens. checking the console i get a 404 for https://server-ip/api/me
i guess that i have to run
php artisan serveto get the api to work? but even then it would only be reachable with http, right?seems like im missing something here, or is https just plain not possible/wanted?
@0xcaff commented on GitHub (Jun 18, 2016):
HTTPS is definitely possible. Try using it with apache or nginx and fasctcgi.
@daniele-athome commented on GitHub (Jun 18, 2016):
@anonaut I had that issue too when running under a subfolder (e.g. /music). Koel works only on the root folder (I had to create an ad-hoc subdomain to host it).
@anonaut commented on GitHub (Jun 18, 2016):
@daniele-athome Yeah, I read trough other issues that running from a webdir other then root folder is not possible. I already deploy koel in the root webdir of my apache installation.
I don't really understand how the routing to the api works, since there is no api folder in the webdir. should there be one?
@daniele-athome commented on GitHub (Jun 18, 2016):
No, it's a virtual path handled by Koel internally. It's probably server misconfiguration. If you are using Apache, ensure that your virtual host has AllowOverride enabled. If not using Apache, you should check the URL rewriting rules of your server of choice.
@anonaut commented on GitHub (Jun 18, 2016):
@daniele-athome Thanks very much, i added
AllowOverride Alland everything worked.