[GH-ISSUE #616] Koel won't log me in... The log page just reloads, then a message flashes on the console ( "localhost:8000/api/data 401 (Unauthorized) ) #440

Closed
opened 2026-02-26 02:33:13 +03:00 by kerem · 5 comments
Owner

Originally created by @they-cloned-me on GitHub (Jun 24, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/616

Originally created by @they-cloned-me on GitHub (Jun 24, 2017). Original GitHub issue: https://github.com/koel/koel/issues/616
kerem closed this issue 2026-02-26 02:33:13 +03:00
Author
Owner

@phanan commented on GitHub (Jun 25, 2017):

OS, browser maybe? I can't help you with this little information.

<!-- gh-comment-id:310889295 --> @phanan commented on GitHub (Jun 25, 2017): OS, browser maybe? I can't help you with this little information.
Author
Owner

@they-cloned-me commented on GitHub (Jun 25, 2017):

Windows 10... I'm sorry if the information is insignificant.. i just don't understand why it happened like that... i had an older version of Koel and it worked fine... but when i cloned the latest version, that problem started

<!-- gh-comment-id:310914613 --> @they-cloned-me commented on GitHub (Jun 25, 2017): Windows 10... I'm sorry if the information is insignificant.. i just don't understand why it happened like that... i had an older version of Koel and it worked fine... but when i cloned the latest version, that problem started
Author
Owner

@phanan commented on GitHub (Jun 25, 2017):

What "older" and what "current" are we looking at then?

On Sun, Jun 25, 2017 at 18:04 fsavalam notifications@github.com wrote:

Windows 10... I'm sorry if the information is insignificant.. i just don't
understand why it happened like that... i had an older version of Koel and
it worked fine... but when i cloned the latest version, that problem started


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/616#issuecomment-310914613, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHrt0kMtcQF7ffW2L2gCLNcng9m88g2oks5sHpMkgaJpZM4OETtm
.

<!-- gh-comment-id:310914708 --> @phanan commented on GitHub (Jun 25, 2017): What "older" and what "current" are we looking at then? On Sun, Jun 25, 2017 at 18:04 fsavalam <notifications@github.com> wrote: > Windows 10... I'm sorry if the information is insignificant.. i just don't > understand why it happened like that... i had an older version of Koel and > it worked fine... but when i cloned the latest version, that problem started > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/phanan/koel/issues/616#issuecomment-310914613>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AHrt0kMtcQF7ffW2L2gCLNcng9m88g2oks5sHpMkgaJpZM4OETtm> > . >
Author
Owner

@they-cloned-me commented on GitHub (Jun 25, 2017):

v3.5.5 (older version)
v3.6.2 (new version)

<!-- gh-comment-id:310914938 --> @they-cloned-me commented on GitHub (Jun 25, 2017): v3.5.5 (older version) v3.6.2 (new version)
Author
Owner

@0xcaff commented on GitHub (Dec 13, 2017):

How are you running koel?

<!-- gh-comment-id:351562155 --> @0xcaff commented on GitHub (Dec 13, 2017): How are you running koel?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#440
No description provided.