You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feishin should not send api requests with old invalid token and kick out out to the server selector.
Current Behavior
Here is the order of requests that happens when starting Feishin when the Navidrome token is expired.
Request
Token
Status
GET /api/album x4
Expired Token
401
Login/Auth
New Token n1
200
GET /api/album
New Token n1
200
GET /api/album x3
Expired Token
401
Login/Auth
New Token n2
200
GET /api/album
New Token n2
200
GET /api/album x2
Expired Token
401
Login/Auth
New Token n3
200
GET /api/album
New Token n3
200
GET /api/album
Expired Token
401
Login/Auth
No token returned
429
DevTools Network tab:
DevTools Console tab:
Steps to Reproduce
Axios error stack :
"AxiosError: Request failed with status code 429 at file:///C:/Users/hoyla/AppData/Local/Programs/feishin/resources/app.asar/dist/renderer/renderer.js:2304:112574 at XMLHttpRequest.h (file:///C:/Users/hoyla/AppData/Local/Programs/feishin/resources/app.asar/dist/renderer/renderer.js:2304:112719)"
Wait for the navidrome token to expire
Startup Feishin
Quickly open DevTools to start the logging of Network requests
Feishin kicks you to the server selector
look in the Devtools network and console
Possible Solution (Not obligatory)
i think it has to do with the old token not qetting cleared or the old requests not being canceled when the new token is gotten.
Context
This is mostly a minor annoyance. It would be nice to have this fixed for a smoother experience with Feishin not having to relog into my server everyday.
Your Environment
Navidrome Docker environment variables:
ND_SCANSCHEDULE: 1h
ND_LOGLEVEL: info
ND_SESSIONTIMEOUT: 24h
Application version (e.g. v0.1.0) : 0.5.2
Operating System and version (e.g. Windows 10) : Windows 11
Server and version (e.g. Navidrome v0.48.0) : Raspberry pi with Navidrome 0.49.3 (8b93962f) in docker container file
Node version (if developing locally) :
The text was updated successfully, but these errors were encountered:
Resolvesjeffvli#403.
This PR introduces a startup check for Navidrome that tries a simple API request (/songs) before loading homepage.
If the check fails, Navidrome API will fallback to trying saved password (if available).
Notes:
- It might also be worthwhile to do a periodic poll?
Expected Behavior
Feishin should not send api requests with old invalid token and kick out out to the server selector.
Current Behavior
Here is the order of requests that happens when starting Feishin when the Navidrome token is expired.
/api/album
x4/api/album
/api/album
x3/api/album
/api/album
x2/api/album
/api/album
DevTools Network tab:
DevTools Console tab:
Steps to Reproduce
Axios error stack :
Possible Solution (Not obligatory)
i think it has to do with the old token not qetting cleared or the old requests not being canceled when the new token is gotten.
Context
This is mostly a minor annoyance. It would be nice to have this fixed for a smoother experience with Feishin not having to relog into my server everyday.
Your Environment
Navidrome Docker environment variables:
The text was updated successfully, but these errors were encountered: