I am seeing a foreign / unrecognized domain coming in.
Are you using a proxy?
If so, did you add your domain cert to PMS so it can handle it?
If not, please do. Let’s see if this helps focus on the root cause.
No proxy set up and I don’t have a custom FQDN pointing to Plex.
I use Cloudflare on port 80 and 443 but it’s not doing anything with Plex.
What domain are you seeing?
Edit: it looks like my home ip. That’s odd, I have Plex set up to treat wan ip as local. And set the subnets correctly.
Redacted:
Mar 11, 2019 18:37:37.618 [0x7fd35e7fc700] DEBUG - HTTP requesting GET https://plex.tv/api/resources.xml?includeHttps=1&auth_token=xxxxxxxxxxxxxxxxxxxx
Mar 11, 2019 18:37:37.649 [0x7fd3d2487700] DEBUG - Request came in with unrecognized domain / IP '100.x.xxx.239' in header Host; treating as non-local
Mar 11, 2019 18:37:37.650 [0x7fd3d2487700] DEBUG - Auth: authenticated user 1 as onedr0p
That’s my current home IP we’re Plex is being hosted. Odd, I have the config for the Plex to treat the wan IP as local.
@onedr0p @ChuckPa
I have looked at the crashes and 8 crash reports were uploaded between 2019-02-22 00:07 GMT and 2019-03-12 09:17 GMT from server
The crashes are within the fmt module which is the same crash that is being followed up on this topic Ubuntu 18.04.2 LTS - Plex Server Crashes - Double free or corruption (!prev)
The development team are trying to reproduce the crash in a debug environment - so any examples of logs with debug enabled leading up to a crash and knowing exact time of a crasj would help look for a common factor
@onedr0p @ChuckPa
I have analyzed dumps for these times - do we have any corresponding server logs ?
Mar 12, 2019 09:17:06 AM UTC
Mar 09, 2019 05:39:38 AM UTC
Mar 05, 2019 03:17:03 AM UTC
Mar 04, 2019 02:55:30 AM UTC
Hi @sa2000 any logs I could grab are ones I posted to this thread. Check my last few posts here. Unfortunately it took me awhile to get them uploaded correctly and we’re wiped after a restart. I don’t have anything earlier than the 9th.
I’m going to enable debug logging and upload any new logs after a crash happens. The odd thing is after updating to the most recent PMS version I haven’t had any crashes. I’m not sure if that is just a solar flare or not but it might be too soon to tell.
ok i will look for them - i just thought you know the timezone your server is on and you could work it out quicker than me as to which logs correspond to the above UTC / GMT times
My server is set to EST. There’s only 1 log on the 9th and 12th posted above.
I have posted this in the other topic for this issue.
Thanks for the help in getting logs that i can match to uploaded crash reports. We have not yet been able to reproduce these crashes in a debug development environment
I have been asked to see if any of you would be able to get a core dump of the crash - preferably on the latest beta. I understand would need to enale core dumps on the system? There is some generic info here: Understand and configure core dumps on Linux - Linux Audit
Plex Media Server Logs_2019-03-18_21-33-42.zip (6.3 MB)
@sa2000 here is a crash with verbose debugging turned on.
I’ll check what is needed to enable core dumps on my server.
Plex Media Server Beta 1.16.0.1220-147963d87 has just been released with the crashes fix
See release note Plex Media Server
- (Playback) The server could crash when a transcode session finished. These manifested as heap corruptions or double-frees (#9801 #9883 #9938 #9940 #9950)
Thanks feel free to lock this thread
