Plex Sending Frequent Crash Reports to sentry.io

General Discussions
1

I run PiHole on my setup and have noticed a big uptick in traffic coming through my network. I narrowed this down to the IP of my docker network, then stopped and started every container until I found Plex as the culprit. ~2,500 times an hour all day every day Plex is trying to send info to o17675.ingest.sentry.io. PiHole is not blocking the transmission.

I’ve downloaded the logs but it’s a lot of data and frankly I don’t know what to look for. I think I’ve narrowed it down to an issue on 2/14. Below is a crash uploader file from 2/14. Through PiHole I can see this is when the problem started. Any suggestions on how to get this to stop? I have no issue reporting small amounts of useful data, but 2,500 an hour is excessive.

Feb 14, 2024 20:59:12.468 [140532994018104] INFO - Crash Uploader - Session Health - Status: crashed StartTime: 1707962352 Duration: 0 UserId: xxxxx Version: 1.40.0.7998-c29d4c0c8
Feb 14, 2024 20:59:12.468 [140532994018104] INFO - Crash Uploader - Platform: Linux ServerUUID: xxxxx UserId: xxxxx Version: 1.40.0.7998-c29d4c0c8
Feb 14, 2024 20:59:12.468 [140532994018104] INFO - Pre-processed minidump directory: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.40.0.7998-c29d4c0c8
Feb 14, 2024 20:59:12.468 [140532994018104] INFO - Post-processed minidump directory: /tmp
Feb 14, 2024 20:59:12.468 [140533026596872] DEBUG - [HCl#1] HTTP requesting POST https://o17675.ingest.sentry.io/api/1233455/envelope/?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Feb 14, 2024 20:59:12.602 [140532993776440] DEBUG - [HttpClient/HCl#1] HTTP/2.0 (0.1s) 200 response from POST https://o17675.ingest.sentry.io/api/1233455/envelope/?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Feb 14, 2024 20:59:12.602 [140533026596872] INFO - Successfully reported session health
Feb 14, 2024 20:59:12.603 [140533026596872] INFO - Crashdump 431081e9-e278-4ef8-dd01098c-7407c5fe not uploaded due to local rate limiting.
Feb 14, 2024 20:59:12.603 [140533026596872] DEBUG - Moved file “/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.40.0.7998-c29d4c0c8/PLEX MEDIA SERVER/431081e9-e278-4ef8-dd01098c-7407c5fe.dmp” to “/tmp/431081e9-e278-4ef8-dd01098c-7407c5fe.dmp”.
Feb 14, 2024 20:59:12.603 [140533026596872] INFO - Crashdump b7e38ac1-d0e9-4e76-788fff87-89200a54 not uploaded due to local rate limiting.
Feb 14, 2024 20:59:12.603 [140533026596872] DEBUG - Moved file “/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.40.0.7998-c29d4c0c8/PLEX MEDIA SERVER/b7e38ac1-d0e9-4e76-788fff87-89200a54.dmp” to “/tmp/b7e38ac1-d0e9-4e76-788fff87-89200a54.dmp”.
Feb 14, 2024 20:59:12.603 [140533026596872] INFO - Crash Uploader - Processing Complete.

2

Anyone have thoughts on a potential solution? It’s frustrating me to no end that I can’t figure this out. Thanks.

3

is “Send crash reports to Plex” enabled in server settings? it is under General under you server name

4

This was originally checked when the problem started. However I have turned this off with no change to result. Toggled on and off a couple times with no success.

5

Are there any crash uploader logs after the 14th?

6

I repulled the logs, all crash logs are from February around the time of the initial incident. If there is something specific in here that would help please point me in the right direction and I’ll pull it.

Screenshot 2024-04-04 at 8.50.34 AM
Screenshot 2024-04-04 at 8.50.34 AM1960×255 68.9 KB

7

So, whenever pms reaches out to sentry.io we generate one of those reports. I will reach out to web to see if they send anything, but i’m also wondering if in something on your system is attempting to resend failed messages? Also, PMS only reaches out to sentry on startup and shutdown/crash so unless your PMS is restarting 2,500 times an hour its unlikely PMS.

8

Maybe this helps. I narrowed it down to Plex by pausing individual containers one by one until I found it. I pause Plex, issue goes away. Restart it and we are right back where we left off. I’m running the plexinc/pms-docker:latest image if that matters. I’ve pulled down new images a couple times with no change.

9

Are you able to validate its sending to https://o17675.ingest.sentry.io/api/1233455 2,500 a day or are you only able to see o17675.ingest.sentry.io? Also, do you have a web browser open to the locally hosted instance of web? i.e. url starts with an ip instead of https://app.plex.tv/?

10

I believe I can only see the domain: o17675.ingest.sentry.io. I don’t know of a way to see the entire address without installing some network monitoring solution.

Plex is accessed thru a browser using a local IP address and port.

11

can you close down all instances of plex in a browser and see if you still see those messages (just trying to figure out what could be sending them)

12

I rarely have Plex open in a browser. It is closed now. I restarted the browser just to make sure. Something is still firing away with requests.

Screenshot 2024-04-09 at 6.04.34 PM
Screenshot 2024-04-09 at 6.04.34 PM618×809 55.6 KB

13

Would you mind grabbing a wireshark capture so we can see the full sentry url? (PiHole only captures the domain)

14

Sorry to say I’ve played with this and can’t figure out how to capture the whole URL. I didn’t think you could do this with HTTPS but I could be wrong. If anyone had a good “how to” they could link here it would be appreciated.