Cannot login: timeout on /login endpoint #1808
Comments
|
try editing data/config.php and change all the sso options to false. it seems one they is causing the timeout.
…Sent from my iPhone
On Mar 16, 2022, at 11:38 PM, Yann Jouanique ***@***.***> wrote:
Organizr Version: 2.1.1690
Branch: develop-v2
WebServer: nginx packaged in official docker image, and Caddy as reverse proxy
Operating System: Official Docker
Problem Description:
Since about a week (probably coinciding with my weekly scheduled restart/upgrade), it is not possible to login to my Organizr server.
The symptom is a timeout on the calls to /api/v2/login - actually an HTTP 504 Gateway Timeout returned by nginx after 60s. The UI shows the 'Login Error API Connection Failed' error toaster.
This happens both through Caddy or directly hitting the container port, in all 3 browsers (FF/Safari/Chrome), after a full cookie cleanup, and a fully container restart/recreate.
My auth configuration is Plex OAuth + local users, and this is affecting both login methods.
Already logged-in users can still connect, but new logins are rejected.
No meaningful container logs:
organizr_1 | Already up to date.
organizr_1 | Adding cron now...
organizr_1 | [cont-init.d] 40-install: exited 0.
organizr_1 | [cont-init.d] 50-debug: executing...
organizr_1 | -----------------------
organizr_1 | | Kernel Info |
organizr_1 | -----------------------
organizr_1 | Linux ae6ff563e8aa 5.11.0-31-generic #33-Ubuntu SMP Wed Aug 11 13:19:04 UTC 2021 x86_64 GNU/Linux
organizr_1 | Time Zone: Etc/UTC
organizr_1 | [cont-init.d] 50-debug: exited 0.
organizr_1 | [cont-init.d] done.
organizr_1 | [services.d] starting services
organizr_1 | [services.d] done.
organizr_1 | Running cron job...
organizr_1 | Running cron job...
organizr_1 | Running cron job...
organizr_1 | Running cron job...
Reproduction Steps:
Login to my server (I can DM some credentials).
Errors on screen? If so paste here:
Login Error
API Connection Failed
I need some help, I really fear I'll be locked out forever...
Many thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
|
Oh you're right, disabling the Tautulli SSO has resolved this! Thx! |
|
@causefx thx for that last comment - i was debugging this for 2 hours... seems tautulli sso is broken atm |
|
@causefx can we prevent sso timeouts from preventing logins entirely? seems tautullis behavior is unexpected, but disabling that function was the last thing i would have checked.. |
|
I will be putting in custom timeouts for each sso item. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Organizr Version: 2.1.1690
Branch: develop-v2
WebServer: nginx packaged in official docker image, and Caddy as reverse proxy
Operating System: Official Docker
Problem Description:
Since about a week (probably coinciding with my weekly scheduled restart/upgrade), it is not possible to login to my Organizr server.
The symptom is a timeout on the calls to
/api/v2/login- actually an HTTP 504 Gateway Timeout returned by nginx after 60s. The UI shows the 'Login Error API Connection Failed' error toaster.This happens both through Caddy or directly hitting the container port, in all 3 browsers (FF/Safari/Chrome), after a full cookie cleanup, and a fully container restart/recreate.
My auth configuration is Plex OAuth + local users, and this is affecting both login methods.
Already logged-in users can still connect, but new logins are rejected.
No meaningful container logs:
Reproduction Steps:
Login to my server (I can DM some credentials).
Errors on screen? If so paste here:
I need some help, I really fear I'll be locked out forever...
Many thanks!
The text was updated successfully, but these errors were encountered: