Sorry Mike but that is a bit of a fundamental statement, I have spent months trying to fix this issue on several instances of PLEX as I say above two production and three test, this is my sixth incarnation!!
Restart the service yes I am not a school boy, I am a sixty year old IT consultant been in the business 35 years… So yes restarted the service dozens of times on each incarnation…!!!
I understand but as you can imagine I have no way to guess you’re a professional working for 35 years in the area, I was simply trying to provide help, and I asked for the output of a command as well not just to make sure you restart.
Its surprising that it all works after restart, which is why I considered the fact that in case the plugin is used maybe it wasn’t doing it on it own (and it should) hence needing manual intervention.
That said, I assume then it should be easy to paste the info I asked before as you can imagine if that shows the port(s) listening that the browser should be capable to reach it, unless there’s a firewall in the middle or some other network conditions at play. Which would be surprising considering you can access it before the upgrade.
So lets get that cleared first please and hopefully get this fixed for you, please post the output of sockstat -l46 after upgrade & restart.
I might need logs after that but lets start there.
Btw since you’re using FreeNAS 11.2 I assume this is on a iocage jail right? (via plugin or created manually) but the though just occurred to me that this might still be an old style “warden” jail?
We only supported 11.2, I don’t recall the exact version but at least since 1.15.0, possibly 1.14.x, some users did report being able to run it on 11.0/11.1 for a while (which doesn’t mean it fully works) there more details on why exactly it doens’t even start now, here: Server doesn't restart after 1.15.6.1079 update [Please Update to FreeNAS 11.2 or FreeBSD 11.2 base]
However I am making some assumptions here, and you did say it starts so this is somewhat confusing and the issue might actually not be the same.
That said its worth checking if that is the case, and if not than grab sockstat -l46
Hi Mike, as an update yes its on an iocage via plugin (not created manually and not in a warden/jail) I also updated the jail two days ago via: “iocage update plexmediaserver-plexpass” which went fine and the server came back ok after restart, but it has done this in the past so will need to try a few times to see if it reoccurs… the only change has been me renaming the server from plex (freenas default) to “plexmediaserver-plexpass” as described in the link I give above
Here is the sockstat you wanted to see many thanks
root@plex:~ # sockstat -l46
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
plex Plex Scrip 52658 4 tcp4 127.0.0.1:58424 :
plex Plex Scrip 52635 4 tcp4 127.0.0.1:58402 :
plex Plex Scrip 52607 4 tcp4 127.0.0.1:58380 :
plex Plex Scrip 52573 4 tcp4 127.0.0.1:58363 :
plex Plex Scrip 52560 5 tcp4 127.0.0.1:58296 :
plex Plex Tuner 52557 13 tcp4 127.0.0.1:32600 :
plex Plex Tuner 52557 70 udp4 *:15572 :
plex Plex Tuner 52557 71 udp4 *:39919 :
plex Plex DLNA 52556 12 udp4 *:1900 :
plex Plex DLNA 52556 15 tcp4 *:1059 :
plex Plex DLNA 52556 18 udp4 *:5424 :
plex Plex DLNA 52556 21 udp4 *:2737 :
plex Plex DLNA 52556 24 tcp4 *:32469 :
plex Plex DLNA 52556 27 udp4 *:54947 :
plex Plex DLNA 52556 30 udp4 *:11726 :
plex Plex DLNA 52556 70 udp4 *:15572 :
plex Plex Scrip 52549 8 tcp4 127.0.0.1:58227 :
plex Plex Media 52516 60 tcp4 *:32400 :
plex Plex Media 52516 61 tcp4 127.0.0.1:32401 :
plex Plex Media 52516 73 udp4 *:32414 :
plex Plex Media 52516 74 udp4 *:32410 :
plex Plex Media 52516 75 udp4 *:32412 :
plex Plex Media 52516 87 udp4 *:32413 :
plex Plex Media 52516 88 udp4 192.168.0.74:10246 :
plex Plex Media 52516 89 udp4 192.168.0.74:64324 :
plex Plex Media 52516 90 udp4 *:1901 :
plex Plex Media 52516 92 udp4 192.168.0.74:60142 :
root@plex:~ #
This all looks ok now, and the sockstat output clearly indicates 32400 is listening. We can also see that the “plex script” processes are spawn and even tunner/DLNA (btw you can disable dlna if you don’t use/need it )
Is it possible that in previous attempts to upgrade PMS you had not run the iocage update yet, and maybe the jail was not on 11.2?
The issue here is that updating PMS it self just needs a pkg upgrade but there was also a iocage update involved, although I don’t see anything harmful in that post, I’m not an expert in FreeNAS so I don’t know if something would cause issues there!
To be honest I much prefer to just have a jail setup (enable VNET) and use pkg install/pkg upgrade instead of the plugin .
In any case 1.16.2 is now in beta and the port was updated already so I suppose we just need to wait for the plugin to update again and see what happens, hopefully it was a one time issue.
Hi Mike,
Thanks for taking a look at the sockstat output, and confirming all look sok, hopefully the renaming the server from plex (freenas default) to “plexmediaserver-plexpass” was the root cause, its been successful one time so lets see if it is consistent… will let you know here…Cheers
I decided to test the PLEX IP interface by fixing an IP and then DHCP, first of all it broke and would not start the PLEX server, then I rebooted the FreeNAS and the PLEX server came up but with still same issue ERR_CONNECTION_REFUSED, so I returned the PLEX config to DHCP, and surprisingly everything worked…!!! Beats me… And now I find out what the bug is in the upgrade… I found the following and the update worked perfectly, pitty I have had months of issues that has taken up so much of my time on this… Getting to the point that PLEX is too fragile and a each time it breaks too much of liability to fix… seriously thinking of stopping my plex subscription!!!
I did a video on something that stopped me from getting in for a month! I work on something until it’s solved. I made this video a while ago just for that. See if this might be your problem:
A toggle I switched on Plex, locked me out… I’m not a Network expert, had to do with SSL I think. But it was my error unbeknownst to me.
Also, is your router port-forwarded on port 32400? You may have completed a firmware upgrade or bought a new router? I’d check that too.
Also, I always keep my updates archived, that way I can always install an old version. Not every version will work – software can get buggy when the leaders want to ramp up their technology. They don’t catch the bugs, usually, until there is a large backlash from the public. It’s why software companies don’t give their emails and phone numbers out anymore, they give us self-help forums instead.
Thank you very much for taking the time to write here, but my situation is a little different as I am using FreeNAS
Also everything worked fine for nearly 0ne year upgrades/updates no issue the problem is in the last four months
Thanks again
What is your platform, and also your NAS?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
