Server Version#: Not getting that far
Player Version#: Not getting that far
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Fresh install on new Ubuntu 22.04 install, PMS is running and listening on IPv6 addresses:
tcp6 0 0 :::32400 :::* LISTEN
but it’s not listening on IPv4 addresses. Nmap portscan confirms that on localhost and LAN subnet. I don’t do IPv6 because my ISP doesn’t, so IPv4 has to work.
This isn’t a user configuration thing: it doesn’t get that far. I presume there’s a config file in the debian package that can correct this but I don’t know where it is.
No, it doesn’t listen on both. I showed you the netstat output. I explained that nmap doesn’t see 32400 open from localhost or other systems on the server’s internal subnet. ← that means IPv4 port 32400 has no listen(3C) socket.
Ed: That output in the op was from:
netstat -an | grep 32400
I’ll wager this doesn’t get regression tested very often. It may have been this way for many builds.
Super easy to test: start an Ubuntu 22.04 VM, add the Plex PPA, install PMS, point a browser at it, be surprised.
I don’t know how to configure Plex w/o the web interface, and I don’t recall seeing a web configuration option to turn off IPv6. Is that really a thing, or are you poking fun? I’m fine w/ torquing settings w/ vim if there’s some documentation on safe/unsafe values somewhere.
That’s great & what I expect, but did you recently (<= days) do a clean install from the PPA and get that behavior. I don’t think this affects existing PMS instances.
I’ve been a Plex fan a loooong time. Your server’s behavior is exactly what I expected. I even did a remove w/ purge, then reinstall. Still no IPv4 listen. I was very surprised.
Ima go edit preferences.xml now. Break EVERYthing.
Fresh installation of 1.40.2 on Ubuntu 22.04.4 LTS (Glockner host)
[chuck@glockner ~.2002]$ dpkg -l | grep plexm
ii plexmediaserver 1.40.2.8395-c67dce28e amd64 Plex organizes all of your personal media so you can easily access and enjoy it.
[chuck@glockner ~.2003]$
Top of the first log:
Jun 01, 2024 20:29:22.441 [140500859226768] DEBUG - HttpServer: Listening on IPv6 as well as IPv4.
Jun 01, 2024 20:29:22.442 [140500859226768] DEBUG - HttpServer: Listening on port 32400.
Jun 01, 2024 20:29:22.442 [140500859226768] DEBUG - HttpServer: Listening on port 32401
You can see the dual-stack socket.
[chuck@glockner ~.2003]$ netstat -an | grep 32400
tcp 0 0 192.168.0.20:48516 192.168.0.191:32400 ESTABLISHED
tcp 0 0 192.168.0.20:39928 192.168.0.60:32400 ESTABLISHED
tcp 0 0 192.168.0.20:32980 192.168.0.70:32400 ESTABLISHED
tcp 0 0 192.168.0.20:46650 192.168.0.50:32400 ESTABLISHED
tcp 0 0 192.168.0.20:45004 192.168.0.17:32400 ESTABLISHED
tcp6 0 0 :::32400 :::* LISTEN
tcp6 0 0 192.168.0.20:32400 192.168.0.20:60252 TIME_WAIT
tcp6 0 0 192.168.0.20:32400 192.168.0.50:56918 ESTABLISHED
tcp6 0 0 192.168.0.20:32400 192.168.0.13:45342 ESTABLISHED
tcp6 0 0 192.168.0.20:32400 192.168.0.70:38704 ESTABLISHED
tcp6 0 0 192.168.0.20:32400 192.168.0.191:34310 ESTABLISHED
tcp6 0 0 192.168.0.20:32400 192.168.0.60:41638 ESTABLISHED
tcp6 0 0 192.168.0.20:32400 192.168.0.13:34548 TIME_WAIT
tcp6 0 0 192.168.0.20:32400 192.168.0.20:60248 TIME_WAIT
tcp6 0 0 192.168.0.20:32400 192.168.0.17:58262 ESTABLISHED
[chuck@glockner ~.2004]$
Now we need to figure out what’s going sideways with your installation.
You have a v6 address. I don’t. Maybe mine was stumbling because I don’t have a v6 address configured, and v6 is enabled by default in PMS? Doesn’t sound impossible, explains the behavior before / after my Prefs change.
Sorry, did the sleep thing. Everyone’s still asleep here & doggo wakes everyone if anyone does anything. I’ll grab the log later this morning. This is interesting.
Full disclosure: this distro is Zentyal 8.0’s iso. They don’t use network manager which may explain the absence of a v6 address.
A bug, yeah, but limited distros affected. So yay? Simple test will fix it:
FYI–
I see you’re been using Mint and not Ubuntu. Mint is not supported because it’s too unstable and predictable as a server distro (derived from Ubuntu). We don’t know what they’ve done but commands I ran on Mint did not return the same results as when typed on Ubuntu or Debian.
Mint seems to be OK for desktop use but definitely not as Plex server. I can’t tell you how many times, while trying to solve a problem, I was told we were using Ubuntu until I challenged and then told “Mint, It’s a derivative of Ubuntu”.
Derived – yes. Function the same – no.
If you want the GUI, great – No problem as a workstation.
As a server, you get the weird crap like what we just fought through.
As for this Distro which I’ve never heard of?
Regret to inform –
Get Ubuntu Server and be done with it . Mint or Zentyal won’t be supported.
You can always install the GUI. sudo apt install gnome
– There are several different desktop managers & styles if you don’t like the Ubuntu gnome. I use the original ‘gnome on Xorg’ layout.
Yeah, but Mint was only a stopgap while the folks in Shenzhen were building this new system.
Now it’s on a Zentyal distro based on Ubuntu 22.04.4. My Plex server has to earn its keep, so it has to serve a few hundred other purposes. I totally understand it isn’t supported. That would be impossible unless you hired a few thousand people to answer dopey questions like mine. But wait: this gets better.
As for THIS issue, let’s just say that my wife didn’t know what I was working on, and she wanted to watch a movie, couldn’t get Plex to work, checked the router and saw the port forward to that Mint machine was gone, so she added a NAT rule to point to the Mint system – which was powered off.
So yeah, this new box could listen all it wanted to but requests on port 32400 were forwarding to a system that was powered off. There’s no obvious indication that this is happening, by the way. My wife happened to mention that she changed a NAT entry, or I’d still be scratching my head on this.
Until such time as it’s vetted, it will not be supported.
Given this is a new OS Distro, I suspect it’s going to take time to stabilize before it can even be tested.
Understand, Mint has been around a lot longer and it couldn’t pass the test.
