-
Notifications
You must be signed in to change notification settings - Fork 1
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
SSO issues after server crash #211
Comments
What exactly are you doing when the server crashes? Are you restarting plappa? The logs indicate that the server is returning HTML instead of JSON, which usually indicates that the request is not sent to the correct endpoint (i.e. wrong port or protocol. |
I believe the crashes are related to advplyr/audiobookshelf#3565 And no, I don't do anything in plappa after ABS has been restarted. I get an error saying it's unable to connect to the server (sorry didn't take screenshot) even after restarting the app. So I sign out, type in the url. And normally it prompts to sign in with OpenID. But it don't. Unless I uninstall and reinstall. I have had two other users experience this over the last couple months. But I've only just moved to IOS and this is my first instance of this problem |
Those should be fixed with ABS 2.16.2. How do the logs look before trying to log out and back in again? This didn't happen on any of my devices when experimenting with 2.16.1 even after tens of server crashes, so I'm assuming it's something about your specific setup that causes this. |
That's a good point. As it's been happening for a couple months whenever I have noticed the docker container has stopped Here are the logs after reinstalling and logging in
|
That is before the server crashed? |
The previous logs are after a successful login after a reinstall right now |
When my ABS crashes for a random reason. Even after resolving the server issue, plappa does not reconnect automatically. When I sign out to re-sign back in. Plappa does not start my OIDC login via Authelia again. I have to uninstall the app and reinstall to have it work again.
The text was updated successfully, but these errors were encountered: