On TrueNAS your jail is on 192.168.1.x/24.
But your router claims that the 192.168.1.x IP address is not on the same subnet.
Is that deliberate?
What is the IP address of the LAN interface of the router?
Do you have multiple network interfaces on the TrueNAS host?
Do you have multiple routers?
(If you draw a picture showing connections and IP addresses, that might help.)
Definitely not. Ignorance remains supreme here.
No multiple routers, AFAIK.
NBN connected Router; that pumps out wifi to personal pc, and personal server (Truenas / Plex) directly connected via ethernet to router.
Truenas network summary:
No static routes, dynamic dns (dunno if I should make static etc?) one interface.
Thatâs interesting. I think port forwarding, at least, was working with UPnP - per the screenshot, the router heard the message from Plex, and opened the port.
Thatâs also interesting; it seems like the router is being a turd, and complaining about the manual port-forwarding IP address even though itâs on the same subnet.
On the Virtual Servers tab, are there multiple interfaces available in the Interface Name pulldown?
Can you share a screenshot of what youâre trying to enter on the Virtual Servers tab, before it barfs with that error?
(Itâs worth restarting the router, too.)
I have a TP-Link over here and I also think I had an issue with manual port forwarding for Plex when I tried it. UPnP worked fine, though.
@Conzaaa The network interface of the entire NAS is âre0â but youâre using VNET on the jail. If you check the âipv4_interfaceâ option do you have an actual item listed as âvnetâ? That was one thing about your screen shot on post 13, there were several fields listed as â-----â or âautoâ and maybe weâre putting too much faith in the jail to do things fine on its own.
The jail settings seem OK - the jail is getting an address from DHCP, which implies jail connectivity is working.
Plus he can connect to the Plex UI, which also implies itâs working. 
True. If the Plex interface is showing it has remote access, it should be working. Might be ones of those causes where a full reboot of the TrueNAS device is in order. Starting and Stopping jails is fine and all, but sometimes things just magically resolve when you reboot from 0.
After that might need to look at it from the (remote) client side and see what the logs are saying.
Right, it was automatically picking up Plex and popping up in UPnP. But when testing the port - would deny it was open, and obviously couldnât access outside network (think I was doing that correctly).
When I try enable, I get the error. Nothing else available on the âinterface nameâ pulldown. Just the âewan-ipoe_dâ thing.
Your screenshot shows the IP as 192.161.1.114 as the IP youâre forwarding to. Not 192.168~
It did, I think I tried that - âvnet0â becomes an option when no DCHP and VNET is selected.
I tried putting 192.168.1.114 (jail IP?) in the IPv4 addrss - and IPv4 netmask as 24, and empty⊠then put same in ipv4 in the default router, but no worky. But wonder if I did something wrong.
No ipv6 autoconfigure.
Its 'flakey" like it shows as accessible for a little while, then often goes to negative, no access. Real odd.
Oof, haha. Ok, think that was just because I wanted to save the general info when I was getting the error other times. But interestingly, changing that - yes, did not get the error for port forwarding from router.⊠but same thing still happening; it shows as connected available for a few seconds, then drops to:
Iâll try stopping everything now, and then rebooting everything.
I would just let UPnP set up the port forward if itâs able to work and give you a green passing arrow back in the Plex remote access settings.
If you turn off the DHCP Autoconfigure on the jail settings you will want to set up all the info there, including the default gateway, but if DHCP is working for local access there isnât really a need for that.
Have you been testing the remote access on multiple clients, in multiple locations? I ask this as I came across someone on Reddit having an issue with remote access. He was trying to access Plex from work and it wasnât working. But this was the only place he was using for testing. When I suggested he try somewhere else, it was fine, so the issue was his employer was blocking it somehow and he didnât realize it because it was the only way heâd checked.
Oooh, after resetting everything. No UPnP still, just forwarding and rebooting - now accessible.
Trying from my mobile (like last time), now works! [EDIT: was green for like 2 minutes, now showing âXâ and Not available outside your network". But it seems like on my mobile, I can still access movies etc? When not on wifi of course, just data].
Indicated : indirect playback though (so this is getting played from plex servers, not my own?)
I change âenable manual connectionsâ to on, and connection 1: IP: what is basically in âpublic IPâ for remote access? then same port?
Connection 2 matters? Or not?
Manual connections is a client setting. It would be setting up a connection without using Plexâs systems to find the server basically. So if it was a remote server, youâd use WAN (Internet) IP of the other person, and the port their router is forwarding in from (so 32400 if it was a âstraight throughâ forward, or the other external port number if itâs not).
If you were using manual connections just within your local LAN, you would enter 192.168.1.114 and 32400 for the port. And then you would be able to access your sever inside your home even when Plexâs systems are down.
Connection 2 is just a place to enter a second server.
Yes, Indirect means Relay, through the Plex servers instead of Directly. It works, but itâs got bandwidth limitations - everything looks like a potato.
Does the public IP address that Plex shows in Remote Access (121.x.x.x) match the IP that is shown at https://canyouseeme.org/?
Does the port that shows in Plex Remote Access match the port thatâs being forwarded in the router?
Can https://canyouseeme.org/ hit that port?
To add to this, does the 121. IP address also show up on your internet connection status on the first page after you sign into your router.
I know you said you only have one router â but itâs also possible your modem is not operating bridged.
Now its not working on my mobile anymore/ âNo internet connectionâ âIt looks like youâre offlineâ âretryâ.
Nothing changed from mobile phone side, or server etc. Truenas, Plex, and jail up as before (after working from reset).
I tried on my wifeâs mobile to manually connect to own server via manual connections on her iphone, and putting in the 121.200⊠with port 32400 did not work either.
It does when I am viewing that from my personal pc with proton VPN off.
Nein.
Within local LAN is when connected to the network via wifi yeah?
But with âremote accessâ I want to be able to access directly when in e.g. an airbnb, on a plane etc⊠to my own server, I should be putting in that 121.200.X.XXX though, right?
But youâre saying on local, I should also put the: 192.168.1.114 and 32400 for the port as a manual connection?
Hey, in that screenshot of the Virtual Server config, thereâs a checkbox for Enable this Entry.
Is that, like, checked? Now that youâve got the right IP address entered.
Or are you using UPnP again? Iâm not sure where youâve got it right now.
My next request will be for you to share server logs.
Using a direct IP for remote access requires you to have a static IP pretty much. Otherwise every time your IP lease rolls over with your internet provider the IP might change and then the settings donât work.
Donât worry about the Direct Connection settings for now. I have a dynamic DNS service set up and reverse proxy for other servers on my TrueNAS system and I still donât even bother with adding Plex to it. The Plex companyâs own solution works fine so I leave it as is.
Ooo. Nice catch. Yeah â thatâs off (light bulb with the no sign on it).
Agreed. 99% of the time those should be blank.
