mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #1281] Audio not working in Browsers except Firefox #733
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#733
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 @abhishekdoshitr on GitHub (Feb 17, 2021).
Original GitHub issue: https://github.com/koel/koel/issues/1281
Hello,
All works good in Firefox, but when I try to use Koel in Chrome/Edge Browser, Audio files not working, even Progress Bar not working.
I don't know whether there is some issue from my NodeJS setup or something, but while I click on Marvelous Visualizer sound is working normally on both Edge and Chrome. I may can give my username & Password here if anyone want to check.
Host :: http://65.1.46.104:8000/#!/search
User :: abhi.doshi09@gmail.com
Password :: Test@1234
@BrookeDot commented on GitHub (Apr 16, 2021):
Hi,
Can you check Edge and Chrome's console for any errors? Both of those browsers are Chromium based where Firefox is not. It sounds so if there are other non-chromium based browsers you can try that would also be helpful.
As you mentioned, this is working in chromium based browsers for others so it may be specific to your setup. Please provide more details on what version of the stack, of Koel, etc you are using where you are seeing this.
The more details you can provide the better position they community will be to help you out.
@BrookeDot commented on GitHub (May 6, 2021):
I'm going to close this out as I have been unable to replicate. If you have more details feel free to re-open.