New FreeNAS server does not allow remote access

[geopfarth]

I built both a new IOCAGE jail and an old cage to see if there was any difference, but I can't find any. Both versions come up internally just fine, I attach the media folders and do all of the internal configurations I need, but when I try to make the server available remotely it will not connect. I have set port translation on my router to multiple different ports from 32400 up. I checked using canyouseeme.org and it looks like the port is available:

Here are the settings from my router. 214 is available remotely the other 2 aren't:

Is there a tunable or setting on 11.1-U2 I need to tweak?

 

[nojohnny101]

As is required for all posts on here, please post full hardware specs and FreeNAS version.

I don't really understand what you want to do. Are you trying to allow remote SSH access to your FreeNAS box? If so, that is a big NO NO. Are you referring to remote plex? I'm confused.

 

[geopfarth]

As is required for all posts on here, please post full hardware specs and FreeNAS version.

I don't really understand what you want to do. Are you trying to allow remote SSH access to your FreeNAS box? If so, that is a big NO NO. Are you referring to remote plex? I'm confused.

My full system specs are in my signature:
FreeNAS Version: 11.1-U2
Case/Chassis: Supermicro SYS-6027R-3RF4+
MOBO: Supermicro X9DR3-LN4F+
CPU: 2 x Intel Xeon E5-2650 V1 Octo core 2.0 Ghz
RAM: 96GB DDR3 Registered ECC
RAID/HBA: 1 x LSI 9211-8i HBA JBOD
HD: 8 x 4TB WD RED 5400RPM RaidZ2
boot drives : 2 x SANDISK 16GB Cruzer USB Flash

I apologize for the confusion. I was trying to stand up a new IOCAGE jail for Plex because I just did the upgrade to 11.1. After standing up the new Plex server I tried to set it to be available remotely and that is failing. I have used port translation at my router so I can run multiple Plex servers and use different external ports (32410 for instance) and those appear to be unblocked by my ISP when checked at canyouseeme.org.

I spun up a third Plex server on the old warden jails to see if I had missed any settings or forgot something, but I had the same issues as I had with the new IOCAGE jail. The goal is to migrate all of my jails to IOCAGE, but I don't want to do that if I continue to have issues with remote access to the Plex server. I am most definitely NOT trying to get remote access to the FreeNAS server, just the Plex.

 

[nojohnny101]

Couple of things:
Can you confirm that your plex jail can reach the internet? That is the first thing I would test.
Secondly, which tutorial did you use to setup your plex jail? There are some oddities right now with the Beta UI and setting up iocage jails (one reason I have avoided doing it yet) so I would google on here for other topics surrounding plex and iocage, you'll find a lot of them. There are some specific networking settings that from what I understand, can't be set from the GUI but need to be set from the CLI. They are not overly difficult commands, one or two lines if I remember.

 

[geopfarth]

Yes, all 3 can reach the internet. I followed Pentaflake's resource for the IOCAGE jail, including the extra commands he noted were required due to a bug in the 11.1-U2 version.

Code:

root@AlenFlix3:/ # ping 8.8.8.8												 
PING 8.8.8.8 (8.8.8.8): 56 data bytes										   
64 bytes from 8.8.8.8: icmp_seq=0 ttl=252 time=27.810 ms						
64 bytes from 8.8.8.8: icmp_seq=1 ttl=252 time=28.227 ms						
64 bytes from 8.8.8.8: icmp_seq=2 ttl=252 time=28.748 ms						
64 bytes from 8.8.8.8: icmp_seq=3 ttl=252 time=29.185 ms						
64 bytes from 8.8.8.8: icmp_seq=4 ttl=252 time=27.604 ms						
64 bytes from 8.8.8.8: icmp_seq=5 ttl=252 time=28.169 ms						
64 bytes from 8.8.8.8: icmp_seq=6 ttl=252 time=28.553 ms						
64 bytes from 8.8.8.8: icmp_seq=7 ttl=252 time=29.459 ms						
^C																			 
--- 8.8.8.8 ping statistics ---												 
8 packets transmitted, 8 packets received, 0.0% packet loss					 
round-trip min/avg/max/stddev = 27.604/28.469/29.459/0.603 ms				   
root@AlenFlix3:/ #															 

 

[nojohnny101]

Can you post an "ifconfig" of your plex jail that is not working?

Strange how you plex remote is not working but it can reach the internet. If the nameserver or the DNS weren't set right then that wouldn't work. It has to be port issue. Are you confirmed that your plex jail's IP is static and match to the port forwarding rules?

Another member on here had problems with plex remote and after confirming all of his settings were correct a final reboot of the router and the server got everything working. Once you confirm your settings, you could try that.

 

[geopfarth]

I agree it is strange. Here is the ifconfig from the warden jail:

Code:

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															 
epair3b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500   
	   options=8<VLAN_MTU>													 
	   ether e2:d7:14:1e:80:6b												 
	   inet 192.168.0.210 netmask 0xffffff00 broadcast 192.168.0.255		   
	   nd6 options=9<PERFORMNUD,IFDISABLED>									
	   media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)					 
	   status: active														 
	   groups: epair														   
root@AlenFlix3:/ #

here is the the ifconfig from the iocage jail:

Code:

Last login: Wed Feb 28 15:15:04 2018 from 192.168.0.2
FreeBSD 11.1-STABLE (FreeNAS.amd64) #0 r321665+de6be8c8d30(freenas/11.1-stable): Tue Feb 20 02:38:09 UTC 2018

		FreeNAS (c) 2009-2017, The FreeNAS Development Team
		All rights reserved.
		FreeNAS is released under the modified BSD license.

		For more information, documentation, help or support, go here:
		http://freenas.org
Welcome to FreeNAS

Warning: settings changed through the CLI are not written to
the configuration database and will be reset on reboot.

root@freenas:~ # iocage exec plex 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:14:fa:0a
		hwaddr 02:13:a0:00:0b:0b
		inet 192.168.0.214 netmask 0xffffff00 broadcast 192.168.0.255 
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair 

root@freenas:~ # 

Here is the ifconfig from the functioning Plex server. It is also running on an older warden jail, and it is available remotely:

Code:

root@plex-standard-jail:/ # 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 vhid 7								
	   nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>							   
epair1b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500   
	   options=8<VLAN_MTU>													 
	   ether 7a:10:5c:ea:25:d2												 
	   inet 192.168.0.212 netmask 0xffffff00 broadcast 192.168.0.255		   
	   nd6 options=9<PERFORMNUD,IFDISABLED>									
	   media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)					 
	   status: active														 
root@plex-standard-jail:/ #

 

[geopfarth]

On the strange new development front; the Plex running on the Warden jail (.210) is now accessible remotely. I'm at a loss as I didn't even reboot the router, jail or host between the time I last checked the server and tonight when an extra server showed up in the Plex app on my TV. I am still unable to get the iocage jail version of the Plex to show up remotely.

I thought there might be a chance that the parental controls on the router might be interfering, but I explicitly exempted the Plex servers and I have seen no change.

 

[nojohnny101]

Sorry I've been busy with school. Hmm. Now I'm really stumped. And you tried rebooting everything after confirming your port forwarding rules on your router match the correct IP addresses of your plex jails?

Sorry I wish I had more ideas.

 

[geopfarth]

No worries, this is a hobby and not my day job so any help you give is greatly appreciated!
I'm out of ideas as well. It looks as if everything is set up correctly. I disabled all parental filters and tried again but still had no luck.
I checked the port translation rules on the router again, and I am certain they match up. The iocage Plex is at 192.168.0.214, the external port is 32414 and the internal port is 32400. I can ping outside and I even know DNS is translating correctly from the server. Canyouseeme.org verifies that port 32414 is open.

Code:

root@freenas:~ # iocage exec plex 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:14:fa:0a
		hwaddr 02:13:a0:00:0b:0b
		inet 192.168.0.214 netmask 0xffffff00 broadcast 192.168.0.255 
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
		groups: epair 

root@freenas:~ # iocage exec plex ping google.com
PING google.com (172.217.11.174): 56 data bytes
64 bytes from 172.217.11.174: icmp_seq=0 ttl=252 time=28.697 ms
64 bytes from 172.217.11.174: icmp_seq=1 ttl=252 time=29.291 ms
64 bytes from 172.217.11.174: icmp_seq=2 ttl=252 time=31.638 ms
64 bytes from 172.217.11.174: icmp_seq=3 ttl=252 time=28.251 ms
64 bytes from 172.217.11.174: icmp_seq=4 ttl=252 time=28.642 ms
64 bytes from 172.217.11.174: icmp_seq=5 ttl=252 time=28.857 ms
--- google.com ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 28.251/29.229/31.638/1.120 ms

 

[mysticpete]

Di you fix this, I have exactly the same problem on a new iocage load 11.2 steady, my old Plex still can be seen externally on 32400 but the new iocage just drops out after a second or two?

 

[Skro]

my old Plex still can be seen externally on 32400 but the new iocage just drops out after a second or two

Do you have both jails on at the same time? Two separate instances can't both be listening on the same 32400 port. Also, did you forward your port to the new Plex jail IP and remove the port forwarding for the old Plex instance in your router?

 

[Skro]

Also, when I set my new plex server up on 11.2, I had to go through the Remote Access set up a couple of times before it 'took'. It seemed to take a little longer than other times Ive done it.

 

[Jailer]

Di you fix this, I have exactly the same problem on a new iocage load 11.2 steady, my old Plex still can be seen externally on 32400 but the new iocage just drops out after a second or two?

You should start your own thread. This thread is nearly a year old and the OP was running a different version of FreeNAS than you are.

 

[mysticpete]

Do you have both jails on at the same time? Two separate instances can't both be listening on the same 32400 port. Also, did you forward your port to the new Plex jail IP and remove the port forwarding for the old Plex instance in your router?

No I changed the port to 34750, also changed all the port forwarding instances, my router picks it up via UPNP anyway so all was good, I also tested with the old jail stopped and rebooted and flushed the router, same issue. Oh also found that I have a double NAT!!

 

[mysticpete]

Also, when I set my new plex server up on 11.2, I had to go through the Remote Access set up a couple of times before it 'took'. It seemed to take a little longer than other times I've done it.

Yes I tried the remote access setup many times and it sometimes takes for about a second then drops out.

 

[mysticpete]

You should start your own thread. This thread is nearly a year old and the OP was running a different version of FreeNAS than you are.

But he replied so all good :)

 

[whiskeysquirrel]

Yes I tried the remote access setup many times and it sometimes takes for about a second then drops out.

mysticpete, et al - any luck? I'm having the same exact problem, plex won't show that its available using direct remote connections. I know for a fact that the port forwarding works, since i can access the plex server page over 4g. Doesnt look like there are any default fw/iptables so im stumped. I'm thinking its a plex issue

 

[mysticpete]

Mine has been working fine now for some time, but I couldn't say what cured the issue, I also changed internet provider so I no longer have a double NAT which means I have remote access now.