Skip to content
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

Web-player idle timeout settings #101

Closed
bubblesnout opened this issue Mar 18, 2020 · 5 comments
Closed

Web-player idle timeout settings #101

bubblesnout opened this issue Mar 18, 2020 · 5 comments

Comments

@bubblesnout
Copy link

While the web player in Navidrome is very simple it fits my needs perfectly. The only issue I have with it is if I have to pause for a while when I come back and press play I'm automatically logged out which is just a bit annoying.

Understandably this is a security feature, but would love it if there was a way to disable or increase this timeout to prevent this from happening.

@deluan
Copy link
Member

deluan commented Mar 19, 2020

This timeout is currently 30 mins after the last interaction with the UI or the last song played. If you pause for more than 30 minutes, your session will be terminated.

I'll make this timeout configurable, but still have to figure out what is the best approach. This is related to the #60 issue.

@deluan deluan closed this as completed in faac303 Mar 19, 2020
@deluan
Copy link
Member

deluan commented Mar 19, 2020

Now there is a new config value, "SessionTimeout". Can be set as an env var like:
ND_SESSIONTIMEOUT="24h"

It accepts the GoLang Duration format: https://golang.org/pkg/time/#ParseDuration

This will be in the next version, release will be probably tonight or tomorrow

@bubblesnout
Copy link
Author

Thanks so much for sorting this out so quickly! I've pulled the latest source and entered the ND_SESSIONTIMEOUT env var and will give it a test.

@bubblesnout
Copy link
Author

(works like a dream, thank you!)

@deluan deluan mentioned this issue Apr 24, 2020
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants