-
Notifications
You must be signed in to change notification settings - Fork 10
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
token expires very frequently #42
Comments
Is this in an instance you are hosting or the publicly hosted instance? The publicly hosted / demo instance may lose tokens stored in the backend due to the hosting plan. |
Publicly hosted, I haven't realized I can host an instance.
…On Thu, Dec 26, 2024, 09:54 Brent Vollebregt ***@***.***> wrote:
Is this in an instance you are hosting or the publicly hosted instance?
The publicly hosted / demo instance may lose tokens stored in the backend
due to the hosting plan.
—
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4W7YGXCDUCRQSJW2NIPCL2HO75PAVCNFSM6AAAAABT7JKH7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRSGMZTEOBZGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I imagine the public instance is restarting and losing your token. You could try running your own instance locally using the instructions in the README. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I haven't measured it yet but I find I often have to log in to spotify because the token expires.
The text was updated successfully, but these errors were encountered: