FreeNAS ERR_CONNECTION_REFUSED

Plex Media Server NAS & Devices
1

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

Hi
I’ve read a few posts with the same error but their troubleshooting hasn’t led me to a fix.
Server was working fine one day, turn it on the next and I can’t access the Plex web interface via ip::32400/web as it comes back with ERR_CONNECTION REFUSED in Chrome.
Tried restarting the server, tried looking at the logs but they stopped updating on the 4th at 09:00. I’m sure this was after the access issues but can’t remember.
I’ve created a new iocage jail and installed the plex plugin again and this works fine (had issues with “Match” working but followed this vid to sort that.)
I’ve gone into the jail’s shell and ran sockstat -l46 and it returns empty.
Ran netstat -r -n , looks the same as the test Plex Plugin

plex_2 - Original currently not working
plex-plexpass - New and working

Server Output

root@plex_2:~ # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: lo
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:60:38:24:6c
hwaddr 02:7c:d0:00:08:0b
inet 192.168.35.25 netmask 0xffffff00 broadcast 192.168.35.255
nd6 options=1
media: Ethernet 10Gbase-T (10Gbase-T )
status: active
groups: epair

root@plex_2:~ # netstat -r n
netstat: kvm not available: /dev/mem: No such file or directory
root@plex_2:~ # netstat -r -n
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 192.168.35.1 UGS epair0b
127.0.0.1 link#1 UH lo0
192.168.35.0/24 link#2 U epair0b
192.168.35.25 link#2 UHS lo0

Internet6:
Destination Gateway Flags NetifExpire
::/96 ::1 UGRS lo0
::1 link#1 UH lo0
::ffff:0.0.0.0/96 ::1 UGRS lo0
fe80::/10 ::1 UGRS lo0
fe80::%lo0/64 link#1 U lo0
fe80::1%lo0 link#1 UHS lo0
ff02::/16 ::1 UGRS lo0

root@plex_2:~ # sockstat -l46
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS

root@plex-plexpass:~ # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: lo
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:60:30:63:78
hwaddr 02:7c:d0:00:08:0b
inet 192.168.35.2 netmask 0xffffff00 broadcast 192.168.35.255
nd6 options=1
media: Ethernet 10Gbase-T (10Gbase-T )
status: active
groups: epair

root@plex-plexpass:~ # netstat -r -n
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 192.168.35.1 UGS epair0b
127.0.0.1 link#1 UH lo0
192.168.35.0/24 link#2 U epair0b
192.168.35.2 link#2 UHS lo0

Internet6:
Destination Gateway Flags NetifExpire
::/96 ::1 UGRS lo0
::1 link#1 UH lo0
::ffff:0.0.0.0/96 ::1 UGRS lo0
fe80::/10 ::1 UGRS lo0
fe80::%lo0/64 link#1 U lo0
fe80::1%lo0 link#1 UHS lo0
ff02::/16 ::1 UGRS lo0

root@plex-plexpass:~ # sockstat -l46
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
plex Plex Scrip 17383 4 tcp4 127.0.0.1:45859 :
plex Plex Scrip 16757 4 tcp4 127.0.0.1:41540 :
plex Plex Scrip 16748 4 tcp4 127.0.0.1:21343 :
plex Plex Tuner 5788 11 tcp4 127.0.0.1:32600 :
plex Plex Tuner 5788 65 udp4 *:45046 :
plex Plex DLNA 5787 12 udp4 *:1900 :
plex Plex DLNA 5787 15 tcp4 *:1587 :
plex Plex DLNA 5787 18 udp4 *:7924 :
plex Plex DLNA 5787 21 udp4 *:2691 :
plex Plex DLNA 5787 24 tcp4 *:32469 :
plex Plex DLNA 5787 27 udp4 *:24709 :
plex Plex DLNA 5787 30 udp4 *:62402 :
plex Plex DLNA 5787 65 udp4 *:45046 :
plex Plex Scrip 5778 8 tcp4 127.0.0.1:52712 :
plex Plex Media 5745 60 tcp4 *:32400 :
plex Plex Media 5745 61 tcp4 127.0.0.1:32401 :
plex Plex Media 5745 73 udp4 *:32414 :
plex Plex Media 5745 74 udp4 *:32410 :
plex Plex Media 5745 75 udp4 *:32412 :
plex Plex Media 5745 76 udp4 *:32413 :
plex Plex Media 5745 77 udp4 192.168.35.2:13287 :
plex Plex Media 5745 78 udp4 192.168.35.2:58641 :
plex Plex Media 5745 79 udp4 *:1901 :
plex Plex Media 5745 80 udp4 192.168.35.2:25004 :

2

This means pms never started, you need to try and see why, but before that I would update to the most recent version which you should be able to do via pkg upgrade.

Things you can look into for debbugging:
dmesg -a|grep Plex in the host (do you see any crashes?)

PMS logs inside the jail → /usr/local/plexdata/Plex Media Server/Logs/ (adapt to plexpass if you’re using the plexpass flavour port)

3

Apologies for the delay in reply.
Updated to 1.18.0.1944, although pkg info still shows as 1.16.6.1592, no effect
ran dmesg -a|grep Plex, - no results
Can’t see any logs under /mnt/Media-9-Disk-Array/iocage/jails/plex_2/root/usr/local/
Closest I can find is - /mnt/Media-9-Disk-Array/iocage/jails/plex_2/root/Plex Media Server/Logs but even after the update and restart the log files still haven’t been modified after 4th October

4

Seems like you’re not using pkg to update then ?

5

Also the logs and all data should still be in /usr/local/plexdata or /usr/local/plexdata-plexpass inside “JAIL_ROOT” (/mnt/Media-9-Disk-Array/iocage/jails/plex_2/root/ in you’re case it seems)

Reading back it seems that you might be using alternative scripts to install/upgrade.

The FreeNAS system provides a plugin (It might not be always up to date, particularity for beta) but it should be sabtle. If you don’t know you’re way around FreeBSD and a shell I recommend you stick with that. Beta version are for testing anyway although we always aim for them to be “stable”.

If you still want to go down that route and not use the plugin, then a standard jail should work (making sure vnet is enabled), you can use pkgng or ports to installed/upgrade plex. If you’re using custom scripts or following tutorials I Don’t recommend you do it on a production server before you a least try it out (you can create new jails for that, its one of the advantages of FreeNAS).

Now about the particular issue, which version of FreeNAS are you running?
If you use pkg upgrade in the jail does it offfer to upgrade plex?

6

Apologies, I updated to 1.18.0.1944 using a script - fetch -o PMS_Updater.sh https://raw.githubusercontent.com/luluhoc/PMS_Updater/master/PMS_UpdaterPLEXPASS.sh

FreeNAS Plugin available is the 1.16.6.1592 version

image
image822×592 35.8 KB

Ran pkg uprade in the jail shell and get the below, I had to enable the FressBSD repo in FreeBSD.conf to update it to v1.18 which it looks like pkg upgrade is referencing too and sees it is already v1.18

root@plex_2:~ # pkg upgrade
Updating FreeBSD repository catalogue…
[plex_2] Fetching meta.txz: 100% 944 B 0.9kB/s 00:01
[plex_2] Fetching packagesite.txz: 100% 6 MiB 2.2MB/s 00:03
Processing entries: 100%
FreeBSD repository update completed. 32947 packages processed.
Updating iocage-plugins repository catalogue…
iocage-plugins repository is up to date.
All repositories are up to date.
Checking for upgrades (12 candidates): 100%
Processing candidates (12 candidates): 100%
Checking integrity… done (2 conflicting)

  • openldap-client-2.4.48 [FreeBSD] conflicts with openldap-sasl-client-2.4.48[installed] on /usr/local/bin/ldapadd
  • openldap-client-2.4.48 [FreeBSD] conflicts with openldap-sasl-client-2.4.48[iocage-plugins] on /usr/local/bin/ldapadd
    Checking integrity… done (0 conflicting)
    Your packages are up to date.

Regards,
Andy

7

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