mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #296] error 400 on /api/data after update to v2.2.0 #214
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#214
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 @BenGamma on GitHub (Apr 11, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/296
Hi,
After updated to v2.2.0, I get a 400 error on mykoelserver.com/api/data when accessing the website root.
When trying the url by itself mykoelserver.com/api/data I get
{"error":"token_not_provided"}Any idea on what is going wrong here ?
Thanks !
@BernardGoldberger commented on GitHub (Apr 11, 2016):
I'm not sure if I'm having the same issue but I have a very similar issue, when I load mykoelserver.com I receive
Failed to load resource: the server responded with a status of 401{"error":"token_not_provided"}(was still working fine for me on 2.2.0) but I noticed that if I immediately reload the page that it will load.For me the issue began happening after I increased my music library from 10K songs to 30K.
@phanan commented on GitHub (Apr 12, 2016):
You can't directly access api/data without a token.
@BernardGoldberger commented on GitHub (Apr 12, 2016):
I just reduced my music library and all is good which means that the issues I'm experiencing is definitely related to large libraries.
I will wait till to hear back from @BenGamma and if he is having unrelated issues I will open a separate ticket and include some screenshots.
@phanan commented on GitHub (Apr 12, 2016):
That would be very weird…
@BenGamma commented on GitHub (Apr 12, 2016):
I don't think it is related to music library size. I have less than 2K songs.
In my opinion, the token I need to access the api hasn't been generated.
How is this token generated ?
@phanan commented on GitHub (Apr 12, 2016):
Token is generated when you log in, and is saved in persistent storage for
all future requests.
On Tue, Apr 12, 2016 at 4:48 PM, Benjamin Gammaire <notifications@github.com
@BenGamma commented on GitHub (Apr 12, 2016):
Can I generate it by hand using a command in terminal ? Because I can't access the login anymore
@phanan commented on GitHub (Apr 12, 2016):
You can clear the local storage using Chrome Dev Tool:
[image: Inline image 1]
On Tue, Apr 12, 2016 at 6:45 PM, Benjamin Gammaire <notifications@github.com
@BenGamma commented on GitHub (Apr 12, 2016):
My local storage is clean. You mean that token is saved in local storage ?
I also have this error in the console. Can it be related to "token_not_provided" ?

@phanan commented on GitHub (Apr 12, 2016):
Token is saved in local storage, yes. For example this is mine:
[image: Inline image 1]
That error should be normal if it's triggered from the log in page.
On Tue, Apr 12, 2016 at 7:05 PM, Benjamin Gammaire <notifications@github.com
@BenGamma commented on GitHub (Apr 12, 2016):
I can't see your image 😞
I think to solution to my problem is to generate a token, but how to do this without accessing the login page ?
@phanan commented on GitHub (Apr 12, 2016):
You can't really generate (and use) a token without logging in.
@BenGamma commented on GitHub (Apr 12, 2016):
So from where can this issue comes from ? what do you recommend ?
@phanan commented on GitHub (Apr 12, 2016):
I'd suggest a clean reinstall. Sorry, I can't deduct anything from the provided information.
@BenGamma commented on GitHub (Apr 12, 2016):
Alright, thanks anyway :)
@phanan commented on GitHub (Apr 13, 2016):
Sorry I can't help further :(