and how is this even possible? from one second to another ?!
> Jul 30, 2019 19:24:15.669 [0x7fdbd1e72700] VERBOSE - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
> Jul 30, 2019 19:24:15.669 [0x7fdbd1e72700] DEBUG - Auth: authenticated user 1 as snickers
> Jul 30, 2019 19:24:15.669 [0x7fdbd1e72700] VERBOSE - Auth: Came in with a super-token, authorization succeeded.
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] DEBUG - Request: [xxx.32:38006 (Subnet)] GET /status/sessions (11 live) TLS Signed-in Token (snickers)
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * Host => xxxxxxxx.d5c0b009f19e4bff89d2f08b4dd3e22b.plex.direct:32400
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * Accept-Encoding => identity
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * X-Plex-Platform => Linux
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * X-Plex-Token => xxxxxxxxxxxxxxxxxxxx
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * X-Plex-Client-Identifier => 667ecf9a6a7d4b65a864d92ffe4408be
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * X-Plex-Device => Linux 4.15.0-55-generic
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * X-Plex-Product => Tautulli
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * X-Plex-Platform-Version => 4.15.0-55-generic
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * X-Plex-Device-Name => cloudBox
> Jul 30, 2019 19:24:15.669 [0x7fdbc2de2700] VERBOSE - * X-Plex-Version => v2.1.32
still gets the login … but nothing else? still the same … so i’m in the world between locked out and logged in … ?
never had that many problems with a security “feature” like on Plex … i mean seriously… and not even a single tutorial on how to solve this… how to connect to vpn and so on …
where is the option to disable this ?!
but anyway, this is clearly a bug, since the server was good until today … so maybe a little bit more interest please?
