Spray

Members
  • Posts

    1
  • Joined

  • Last visited

Everything posted by Spray

  1. Hey guys, I've been getting an error that I have been banging my head against that never seen before and can't figure out what is causing it. Here's the error text: 2022-05-21 13:43:19,028 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247462181536 for <Subprocess at 23247462176064 with name plexmediaserver in state STARTING> (stdout)> 2022-05-21 13:43:19,029 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23247462181584 for <Subprocess at 23247462176064 with name plexmediaserver in state STARTING> (stderr)> 2022-05-21 13:43:19,029 INFO exited: plexmediaserver (exit status 255; not expected) 2022-05-21 13:43:19,029 DEBG received SIGCHLD indicating a child quit 2022-05-21 13:43:21,032 INFO spawned: 'plexmediaserver' with pid 82 2022-05-21 13:43:21,128 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: listen: Address in use (N5boost10wrapexceptINS_6system12system_errorEEE) this repeats forever on the official plex docker, and linuxserver repositories, binhex-plexpass cuts it off after like 10 tries. When I click webUI it just lets me open my plex like normal but there is no server so only the plex served media is there. (kinda obvious since the server wont set up) Here's what I have tried: Stopping all proxies / tunnels ( I have been messing around with Nginx Proxy manager and Cloudflared tunnels recently, although plex was still working through my messing around so I don't think this is what broke it, but maybe) Factory resetting Router (thought I may have messed up some firewall rule or something that was messing with it, although it should be local so I also am not sure how that could be) uninstalling / reinstalling docker (both with and without deleting appdata) switching to a different plex repository (they all give the same error) Checked that there were no other dockers using that port (there isn't as far as I can tell) I have some kind of hunch that maybe an old process is running and occupying the port, but I have nothing to back that feeling up, nor would I know what to do about a rogue docker process. Any help would be much appreciated, I am a bit of a networking noob so I need a little push sometimes.