Server Version#: 1.15.6.1079 (after update)
Player Version#: ??
Hi please help, my primary PMS that has been working for about 1 year is installed on FreeNAS 11.2-U4.1, (manual Jail install) as I say been working flawlessly.
I installed a second PMS (different name, through FreeNAS plugin manager) about 4 months ago and after the first update I got this error, I tried to fix it but found no fix that worked so about two months ago I deleted my Test PMS and re installed…
Last week I “pkg update and upgrade” at the jail level, my test PMS went fine and came back working ok, my primary PMS however is failed and I can’t get access to the server web page, I get this error!!!
Hello thanks for your time and reply, the server is actually started, I can’t get to the WI, looking at what you have here will that not uninstall the whole of my PMS and I will lose all the configuration and data?
Hi thanks again, unfortunately as of last night my broadband is faulty and am awaiting it being fixed, will be back later when I can reach the repos, thanks
Hi Now revisiting this topic again… I decided to bite the bullet and simply start from fresh, so in Freenas I deleted my primary and test Plex-pass plugins, I installed from fresh as a Plex-pass plugin, and reconfigured from scratch, took me a week to get this working as I had in the past…
I decided to update as I had been reminded of new version, so yesterday I did said update, I followed the the Xi systems process to update an iocage, and now I get this same error on PLEX… This will be the 6th time I have had to start PLEX from scratch…getting a little tired of this??? how can I get this so plex does not continually fail each time I update…ERR_CONNECTION_REFUSED…???
YES! I am also using a NAS (Western Digital MY CLOUD DL4100). I was a noob and so many were calling this the Network Attached “Server”. Nope! It’s a Storage that uses RAID. I wish I had built my own server.
Anywho! I digress. To the problem.
The WD NAS gets VERY BUSY. I HATE this! And your Access get’s blocked; your router gets clobbered and you have no access. THEREFORE anything trying to access your NAS, can’t get in.
Sometimes it takes a day, two days… hours and hours and hours… for the NAS to calm down and quit syncing. That’s RAID, the reduncancy, but it’s also the NAS capability that hogs its resources and blocks access to folders, to whatever you got in there.
To test this theory, just try to login your NAS when you PLEX is “not accessible”. Or power down your NAS and when the blue light is flashing, you will gain access to all (even PLEX) just before your NAS powers off; while powering down your NAS will quit syncing and pause RAID functions.
I found this out the hard way too. Support? LOL! If it weren’t for Youtube and forums, there would be no HELP at all.
One more thing I forgot to mention! I download the release from PLEX website. When I allow my NAS to “update” my PLEX file, it logs the file into an unknown format and my PLEX doesn’t know what it is. I download the new released version, something like this “PlexMediaServer-1.15.4.919-8e2884e4b-WDMyCloudDL4100.bin”, but if I let NAS download it I get something like “Plex 1.15.6.1079” and it’s NO GO. I can’t currently get into my NAS login, because I can hear my NAS spinning all the drives and the blue lights on each of the 4-drives is flickering.
2nd solution: download the “PlexMediaServer-1.15.4.919-8e2884e4b-WDMyCloudDL4100.bin” bin file from PLEX, and do a Manual Install. Don’t let NAS update it for you. Plex and NAS are two separate entities and they don’t speak the same language and it’s not harmonious; no synergy.
You must use the long bin file version, e.g. “PlexMediaServer-1.15.4.919-8e2884e4b-WDMyCloudDL4100.bin”
Hi Mike, yes its a standard PlexPass plugin v.1.15.6.1079 via an iocag on Freenas FreeNAS-11.2-U5, working fine for about a week then tried to upgrade to 1.16.0.1220, and I get this ERR_CONNECTION_REFUSED…??? immediately after upgrade, thanks
Hi Mike, yes its a standard PlexPass plugin v.1.15.6.1079 via an iocag on Freenas FreeNAS-11.2-U5, working fine for about a week then tried to upgrade to 1.16.0.1220, and I get this ERR_CONNECTION_REFUSED…??? immediately after upgrade, thanks
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!!!
So you actually see the pms process start but can’t reach the server via itts local bundled web app (IP:32400/web), I’m assuming this is where you get the ERR_CONNECTION_REFUSED !?
Hi Mike, as I say it’s all now working no errors, the big test will be the next time I upgrade… as so far in the last three months it has failed after each time I upgrade with this error, 5 times it has happened twice on production and 3 times on test systems…!!
So have to wait for next version to put this to the test… If it fails again I am going to raise a case with PLEX and iXsystems, if it continues I will give up on PLEX and cancel my plexpass.
