-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Session is expired when alt tabbing #214
Comments
I don't think the issue is related to alt tabbing, my thoughts are that it's a permissions related issue that I'm unaware about on Jellyfin. Is the person Feishin accessing your server on an account with limited permissions to your server? |
To my knowledge they have the same permission as most on the server and
it's only them with the issue.
…On Fri, Aug 11, 2023, 11:47 PM Jeff ***@***.***> wrote:
I don't think the issue is related to alt tabbing, my thoughts are that
it's a permissions related issue that I'm unaware about on Jellyfin.
Is the person Feishin accessing your server on an account with limited
permissions to your server?
—
Reply to this email directly, view it on GitHub
<#214 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGYPBCPNBTTPINFDLCES4MLXU34FVANCNFSM6AAAAAA3NM6NNA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Feishin logs you out if you get a Can you have them open the browser dev tools via feishin/src/renderer/api/jellyfin/jellyfin-api.ts Lines 272 to 276 in 663893d
|
It seems in console we have To add as well I have begun getting the same error |
Sorry for the late response, but I believe this may have had something to do with how the app was fetching playlists (not 100% sure). I've added a way to re-authenticate whenever running into the expired session. Going to close this for now, but will we can re-open this if you still experience this after the next release. |
Hi, I hope I am wrong on my end, but from the looks of it, this issue needs to be opened again. I have been getting random "session expired" with the same 401 'unauthorized' as seen here in this issue. I mainly use the Windows version of Feishin, but have seen random "expired" sessions on Mac and in the browser version as well. P.S.: Sorry for only reporting this just now, I was incredibly busy. edit: I'm currently on 10.8.10, as playlists in 3rd party apps haven't been able to show up on that version yet. |
I'm also noticing mysterious "session expired" after long disuse with Navidrome, both Navidrome and Feishin running on Linux. Opening the server edit page and re-saving gets it going again, at least. |
This is not mysterious; Navidrome's credentials are temporary (https://www.navidrome.org/docs/usage/configuration-options/#:~:text=false-,sessiontimeout,-ND_SESSIONTIMEOUT). When you save the password or re-save the server, it generates new credentials. This is unlike Jellyfin, whose credentials do not expire (as far as I understand) |
Session timing out might not be mysterious, what's mysterious is why Feishin does not recreate it automatically like every other client. It has the password and username saved right there, after all. |
If (and only if) you selected save password, then it should reauthenticate on failure. But this could also be blocked by #403 (resolved hopefully by #510). If you're using web, the password is never stored |
I will be closing this issue as the issue in my earlier comment was addressed (and some better fixes done). |
Expected Behavior
Feishin open and use the server
Current Behavior
Feishin will open for a short period of time then when alt tabbing suddenly closes the server and says session is expired. Server is a Jellyfin.
Server crash in Feishin
Unable to atm
Steps to Reproduce
Open Feishin, sign in, alt tab.
Unfortunately cannot yet
Possible Solution (Not obligatory)
Context
Your Environment
-Extra information: this bug report is on behalf of a friend who's struggling to get the app to run properly. I'm making this at work and can provide more information later.
The text was updated successfully, but these errors were encountered: