(BUG) No access anymore. Server still running

Newest Versions

Can not access PMS anymore. Server still running. Edited the Preferences like in the troubleshoot, but does not help. The entries don’t get filled up again. I’m completely on a remote server and i always get redirected to my other servers. Everything else on that server is up and running fine.
Of course i tried the direct IP-Address instead of plex.tv without success neither.
Plex Media Server.log (728.0 KB)
Crash report is not created

Funny fact, nothing happened really Plex related … i just installed a secondary Drive, had a little problem with parted, needed to KVM-Console into it, fixed it, rebooted, all worked fine again - except Plex. WTF?!

is it again this security mechanism?

Would be really thankful if one could help

another one: Plex Media Server.log (2.6 MB)
there are no crash reports

Restart PMS, and after 2 min, try again
Then upload a zip with all the PMS server logs, since they roll over, and we need it from the start to see if it signs into plex.tv correctly

thanks for helping

Logs-PMS-snickers-30-July.zip (4.9 MB)
I personally would bet it’s PMS security on remote servers … don’t know why from one second to another but yeah … problem is, i have no clue how to access my remote server locally … have no clue of that whole machine-to-machine vpn thing … but again, was working till yesterday for years now
had kinda the same problem 1-2 years ago with another server. have you guys already implemented a way to disable/fix this “first connection on local” thing?! because this would explain why it’s not working after the changed of the Preferences.xml

I guess it’s more or less obvious… since the PMS is up and running fine, direct server url directs me to trakt.tv … so …

According to the log, server is fine, and logged in as a user named snickers

Your forum account says snickers_1 so could it be you are trying with your browser been logged into a different account?

no… that was a strange thing with your Forum switch back in the days… plex.tv name is snickers while my forum name got snickers_1 with the new forum. My 1000+ Forum likes are gone too :frowning: ^^

So what can i do now? again, it must be PMS security system … anything else makes no sense…

Heh, and ack :wink:

Try and browse to https://plex.tv/api/resources?X-Plex-Token=XXXX and see in the XML, if the server shows

Replace XXXX in the link with your own token:

the server shows not up
meanwhile the server with direct-ip says “access denied” … so now i know it’s the security system …
so i guess i have to work on some vpn skills to get it working again?!

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?

omg !
on one device, still connected to the server, there is even a playback possible !! going through the menu etc no problem! …
same account, same server, new connection - boom, nothing ! OMG

WHAT IS GOING ON ?!?! THIS IS A CLEAR BUG!

awesome… even this

Open a Terminal window or your command prompt
Enter the following command (substituting the IP address of your server as appropriate):
ssh ip.address.of.server -L 8888:localhost:32400
Open a browser window
Type http://localhost:8888/web into the address bar
The browser will connect to the server as if it were local and load Plex Web App

does not work … directs me directly to plex.tv

So here i have a running PMS not accessible in any way … how to solve this ?

May I augment that SSH tunnel sequence?

  1. ssh -L 8888:127.0.0.1:32400 ip.addr.of.host
  2. Sign in and let it sit
  3. Sign out the local Plex/web (upper right)
  4. Open incognito window
  5. In it, open http://127.0.0.1:8888/web
  6. If not presented properly to that server and accessible: then
    a. sudo tar cfz /tmp/plexlogs.tar.gz "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs"
    b. download and attach that tar.gz here.

In the future, please leave VERBOSE disable unless requested. It generates far too much output plus it diminishes the amount of elapsed time we can see to about 2 minutes elapsed time.

The reason for using IP addresses is simple: Some distros are switching to IPv6 base while others default to the host’s LAN IP. We specifically want the IPv4 loopback adapter at 127.0.0.1

For some reason, you are locked out of the server, so try this:
https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/

And remember to make a backup of the preferences.xml file first!

Then reclaim the server, and for that, I suggest this one:

incognito tab .. obviously, it gets all the Library’s … but nothing more..
does not show up in settings aswell

still nothing …

must be a bug … not security related , i guess

again complete Log folder

plexlogs.tar.gz (7.2 MB)

is it possible to disable verbose via terminal? and btw … shouldn’t be verbose/debug mode the exact right thing right now?

  1. It can be disabled by editing Preferences.xml, removing LogVerbose=“1” when PMS is stopped.

  2. Contrary to thinking, VERBOSE shows packet traffic. We are not debugging packet exchanges here. We are at the much-higher functionality level.

PMS has a 5 roll-over log file buffer (5 MB each) by default. When VERBOSE is enabled, those precious 30 MB are consumed quickly with all the packet info. This is why the elapsed time view window shrinks from 30-60 minutes to 2 minutes.

Plus, there is so much noise with VERBOSE enabled, it’s impossible to keep one’s mind focused on what’s happening.

As additional info, it’s possible to increase the number of log rollover files retained.

I use different versions so keep both forums of it in my Preferences file without ill effect.

add: LogNumFiles="20" NumLogFiles="20" to retain 20 log files. 10 log files is adequate for most users.

Supplemental:

We don’t need to see this detailed amount of traffic: ( i have redacted private info )

The only two statements needed were the two DEBUG statements. We know what’s happening between them when it reports “Completed”.

Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] DEBUG - Request: [XX=XXXX=XXXX=XXXX:54622 (WAN)] GET /library/metadata/595301?includeExternalMetadata=1&includeExtras=1&includeRelated=1&includeRelatedCount=0&includeReviews=1 (6 live) TLS GZIP Signed-in Token (snickers)
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Version => 7.18.1.11300
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Client-Identifier => 5395362b6a517ace-com-plexapp-android
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Device-Name => SHIELD Android TV
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Platform => Android
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Platform-Version => 8.0.0
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Provides => player,pubsub-player,controller
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Product => Plex for Android
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Device => SHIELD Android TV
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Model => darcy
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Device-Vendor => NVIDIA
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Device-Screen-Resolution => 1920x1080 (Android TV)
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Device-Screen-Density => 320
Jul 30, 2019 21:34:53.225 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Username => snickers
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * Accept-Language => de-de
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Features => external-media
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * Accept => application/xml
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * User-Agent => Dalvik/2.1.0 (Linux; U; Android 8.0.0; SHIELD Android TV Build/OPR6.170623.010)
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * Host => XX=XXXX=XXXX=XXXX.d5c0b009f19e4bff89d2f08b4dd3e22b.plex.direct:32400
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * Connection => Keep-Alive
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * Accept-Encoding => gzip
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Token => xxxxxxxxxxxxxxxxxxxx
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * includeExternalMetadata => 1
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * includeExtras => 1
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * includeRelated => 1
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * includeRelatedCount => 0
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * includeReviews => 1
Jul 30, 2019 21:34:53.226 [0x7ff38ea4c700] VERBOSE -  * X-Plex-Token => xxxxxxxxxxxxxxxxxxxx
Jul 30, 2019 21:34:53.230 [0x7ff38ea4c700] VERBOSE - It took 0.0 sec to serialize a list with 1 elements.
Jul 30, 2019 21:34:53.230 [0x7ff38e24b700] DEBUG - Completed: [XX=XXXX=XXXX=XXXX:54622] 200 GET /library/metadata/595301

okay. i understand. will keep it disabled from now on.

with verbose disabled. clicked a bit through the (not accessable) menu’s … hope there are new entries.
plexlogs.tar.gz (7.0 MB)