-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Error 401 #260
Comments
Hey @EinNiki , try logging out and back in, if you are on the login page but are receiving this error, try deleting the token in the local storage. Open your browsers developer tools, go to Application tab, and under local storage |
I made a DashBoard where I use the Jellystat api |
Oh, are you using the api key in your authorization header? Can you provide an example of the api call you setup? |
https://haste.simplecloud.app/awafezuxuv.js |
your api endpoint doesn't look correct, you can reference the swagger docs for the correct endpoints at |
It still doesn't work (I still get "Unauthorized"). Do I have to have a username and password or not? Could you send me a curl or a code sample? |
hello? |
Hey @EinNiki , sorry, just been abit busy so havent had time to reply to issues. or |
curl -X GET "https://subdomain.maindomain.tld/api/getLibraries" works for me, I still had to adjust it a little. |
Not directly related to the OP's situation, but to the error. I noticed that I have to clear browser cache almost every day to access Jellystat web UI without getting 401 errors. Deleting the session cookie also works, but you also have to do that often. Re-logging doesn't seem to do the trick. |
Describe the bug
Cannot connect to API Error code 401
Environment Details (please complete the following information):
Screenshots
![Screenshot 2024-11-06 180902](https://private-user-images.githubusercontent.com/73404542/383659113-ff5a0cd5-44e5-4004-b27e-7aa1eb20c0bb.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxMjM4MjUsIm5iZiI6MTczOTEyMzUyNSwicGF0aCI6Ii83MzQwNDU0Mi8zODM2NTkxMTMtZmY1YTBjZDUtNDRlNS00MDA0LWIyN2UtN2FhMWViMjBjMGJiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDE3NTIwNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBiNGE1ZDQ2YmRiMDc0NDA5YzA5NjYxNGMxM2NhMmU1NTc0ODY4MzMxM2UyNWQzNjc5ZDIyZjM2MzhlMjA0ZDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.6IY8bRStPJWG3OLJtvUHhA1tF0EeHV8f3WKluJm4GbU)
Container Logs
[JELLYSTAT] Server listening on http://127.0.0.1:3000Invalid token
The text was updated successfully, but these errors were encountered: