Server Version#:1.19.1.2645
Player Version#:N/A
I am running PMS on a QNAP TS-231P, but it cannot reach the Internet for remote access - even with a port forward set up on the router. It used to work fine even without a port forward set up until about four weeks ago.
The connection is dead-simple, as the NAS is connected via ethernet directly to an Eero Pro, which is itself connected directly to the ISP modem (and the modem is in bridge mode). There is no double-NAT. uPnP is set up on the Eero. The NAS is using a 1500 byte MTU.
I can see the uPnP discovery is working, as the NAS appears in applications like VLC (although I can’t see any Bonjour/DNS-SD advertisements for it). If I toggle a Plex app on my phone between wifi and cellular, I can confirm that the service is available on the local network, but not remotely. Using a service like canyouseeme.org confirms that I cannot reach the service (even though a port forward is set up using that external port).
I have similarly turned off all the security services, etc, on the Eero in order to test if any of them were interfering…even with the Eero stripped down to just basic routing functions, no dice for remote access.
Now, here’s the ringer…I have another PMS instance, same version, running on a macOS system on my network - and it works perfectly. Don’t even need a port forward for that PMS, straight uPnP works for remote access (and I can also see it in Bonjour/DNS-SD).
I am literally at a loss to figure out what is going on with this PMS instance. As mentioned, up until about four weeks ago it worked just fine for remote access. Both the PMS and the Eero have been updated in between, so I would expect that one of them is the problem…but since the other PMS instance works, I have to suspect that it is something unique to the QNAP linux version of Plex (if the Eero, I would expect both PMS instance to fail in the same way)?
Hi, MwC_Trexx, over the past number of weeks there have been both Plex and QTS upgrades. None were major upgrades, however (Plex within the 1.19.1 sub-version and QTS within the 4.4.2 sub-version). Unfortunately, I was not observant enough - or not checking other settings enough - to see if one of those updates immediately preceded the issue.
I have now also tried rolling back to 1.16.6, which is the latest version in the QNAP store (and then upgrading again through a 1.18.4 version I had downloaded, and then back up to 1.19.1.2645). In all cases, the issue was not resolved.
That being the case, server logs are attached. I was playing around with the remote access switches and some bits suggested by Eero support to see if it helped, so those uPnP calls should be near to the end of the log.
I am similar to old crow.
both qts and plex updates. In a period of 14 days there were 5 plex updates. And a QTS that was withdrawn then a replacement for the withdrawn update.
I updated everytime hoping this one will fix it . It did not happen. !
I just this minute d/l 1.19.2.2673
After install remote connecrtion was red.
Clicked apply atm I have port forwarding set up and remote turned green.
Having port forwarding appears to make no difference on of off remote still drops on and off .
There is a bug with HBS3 that crashing my QTS desktop and my network connections. Usually when running a job but not everytime.
My desktop goes back to default screen and Network and Virtual switches are not connected. - until i click one. Then things appear back to normal…
I have another Qnap NAS, the TVS-1282 which had the same Plex problem just not as often.
I am seeing the same problem with my QNAP server. Running the latest software 1.19.1.2645. I’ve been seeing it work for a few minutes then go red for hours/days at a time. It worked on my Windows version just fine. Sticking to standard port forwarding on 32400.
Haven’t seen anything back since I posted logs…hopefully that’s because folks haven’t had time to look yet and not that there is no info to be found…
In any case, I have other things I need to do on the network and can’t wait indefinitely for troubleshooting. So find att a network diagram of (part of) the current topology (all the rest is also on wifi). As well, it has embedded imagery showing which Plex server can get remote access and which cannot. Maybe that will help someone figure out what isn’t working.
Well, I tried the update, but…sigh…no joy. Still the same situation - PMS on the MBP works no problem, server logs indicate reachability=1 and I can reach it from Plex apps when off my local network on cellular. PMS on the QNAP still says it cannot connect for remote access, and it cannot. Server logs are reachability=0, and I cannot reach the server while off of the local network.
I can only think of three broad possibilities…1) the issue is with PMS (incl something in how PMS accesses networking via macOS vs Linux networking stacks). 2) the issue is with the QNAP Linux networking stack itself. Or 3) the issue is in how Eero handles networking.
#3) seems highly unlikely. Even if there were some issue like a uPnP implementation problem, that shouldn’t effect port forwarding. And the fact that one OS and PMS variant works fine is pretty clear evidence that things are working in the router.
#2) is a possibility, but other services on the QNAP which use uPnP seem to work fine. Now, those are QNAP-developed apps, so it could be that the issue is in whatever public APIs QNAP exposes. But again, it’s Linux, so I would suppose the number of additional private APIs QNAP has in QTS would be minimal…but it seems to be a pretty heavily customized variant.
#1) just seems most likely, especially as the networking code would have to be pretty different. I assume the macOS version of PMS uses Apple’s NS and CF frameworks. And the QNAP version would have to use whatever Linux networking implementation QNAP uses…
Unfortunately, there’s not much else I can do beyond this sort of speculating, except hope that a developer digs in and finds whatever is going on.
