# Plex server crashing

**URL:** <https://forums.plex.tv/t/plex-server-crashing/852790>\
**Category:** Plex Media Server\
**Tags:** server-windows\
**Created:** [September 7, 2023, 5:17pm UTC](https://forums.plex.tv/t/plex-server-crashing/852790 "2023-09-07T17:17:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lazarus\_Long](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/lazarus_long/32/333009_2.png) [@Lazarus\_Long](https://forums.plex.tv/u/Lazarus_Long)\
**Post date:** [September 7, 2023, 5:17pm UTC](https://forums.plex.tv/t/plex-server-crashing/852790/1 "2023-09-07T17:17:42Z")

</div>

Server Version#: 1.32.6.7371  
Player Version#: N/A

I’ve been having issues lately with my Plex server crashing/stopping. I haven’t really nailed down root cause yet but noticed this very odd looking text in one of my Plex Media [Server log](https://support.plex.tv/articles/200250417-plex-media-server-log-files/) files - wondering where it would be coming from?

Sep 05, 2023 23:19:13.543 [7624] ERROR - Error parsing HTTP request: ELP

Sep 05, 2023 23:19:19.968 [14244] ERROR - Error parsing HTTP request:

Sep 05, 2023 23:19:21.781 [7624] ERROR - Error parsing HTTP request: € (rþ † —|  
Sep 05, 2023 23:19:22.243 [7624] ERROR - Error parsing HTTP request: aversionbind   
Sep 05, 2023 23:19:22.702 [14244] ERROR - Error parsing HTTP request: HELP

Sep 05, 2023 23:19:23.169 [7624] ERROR - Error parsing HTTP request: S O ?G×÷º,îê²`~ó ý‚{¹Õ–Èw›æÄÛ<=Ûoïn ( f e d c b a `  
Sep 05, 2023 23:19:23.634 [14244] ERROR - Error parsing HTTP request: i eU§ärandom1random2random3random4 /  
 9 ÿ 0  
, \*   
Sep 05, 2023 23:19:24.099 [7624] ERROR - Error parsing HTTP request: qjn0k¡¢  
¤^0\ a P€ ¢eNM£0 ¡0ekrbtgteNM¥19700101000000Z§¹Ù¨0  
Sep 05, 2023 23:19:24.567 [14244] ERROR - Error parsing HTTP request: ¤ÿSMBr @ @  PC NETWORK PROGRAM 1.0 MICROSOFT NETWORKS 1.03 MICROSOFT NETWORKS 3.0 LANMAN1.0 LM1.2X002 Samba NT LANMAN 1.0 NT LM 0.12  
Sep 05, 2023 23:19:25.030 [7624] ERROR - Error parsing HTTP request: l   
Sep 05, 2023 23:19:25.509 [7624] ERROR - Error parsing HTTP request: OPTIONS sip:nm SIP/2.0

Via: SIP/2.0/TCP nm;branch=foo

From: sip:nm@nm;tag=root

To: sip:nm2@nm2

Call-ID: 50000

CSeq: 42 OPTIONS

Max-Forwards: 70

Content-Length: 0

Contact: sip:nm@nm

Accept: application/sdp

---

<div class="post-metadata">

**Author:** ![BanzaiInstitute](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/banzaiinstitute/32/293273_2.png) [@BanzaiInstitute](https://forums.plex.tv/u/BanzaiInstitute)\
**Post date:** [September 7, 2023, 5:35pm UTC](https://forums.plex.tv/t/plex-server-crashing/852790/2 "2023-09-07T17:35:47Z")

</div>

Here’s another report of the distinctive string `random1random2random3random4` showing up … on someone’s printer … due to a scan from nmap.

> **[Re: Compromised printer? Meraki Go](https://community.meraki.com/t5/Questions-and-Answers/Compromised-printer-Meraki-Go/m-p/116508)**
>
> Bless you! This explains it all. I certainly did not expect this. The reply from my colleague on our Slack channel just now: "oh yeah, today I ran a few nmap scans".    (Yes... I know)   In any case, maybe this thread can be useful for...

Now if Plex actually dies from such a scan, that’s a juicy bug.

Following 🍿

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [December 6, 2023, 5:35pm UTC](https://forums.plex.tv/t/plex-server-crashing/852790/3 "2023-12-06T17:35:54Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.