Server Version#: 1.31.3.6819-2ef591a4c
Player Version#: 1.31.3.6819-2ef591a4c (Plex web)
Every time I enable Remote Access, it’ll say that the server can be reached from the Internet successfully and then after about 30 seconds, it fails. I’ve seemingly tried everything: enabling UPNP, adding the DNS rebind to my firewall, creating NAT rules with a different public port, creating NAT rules with a private public port, trying through my VPN, trying through Comcast …
If I VPN into my network, I can use Plex no problem … but it never works remotely and seems like the port is always closed.
At least from what I can see on my firewall end, the port should be open. I am using a Hitron CODA cable modem which is always in bridge mode.
Not sure what else I can do … I’ve been fighting with this for hours and hours the past few days but haven’t been able to get through.
Other ports that I’ve opened for other apps seem to work just fine but Plex … nope.
To add: I’m using Pihole for DHCP and DNS but I’ve got all Plex domains whitelisted (including the analytics.plex), OPNsense as the main firewall, a USW-48-PRO Unifi POE+ switch.
I’ve tried setting this whether on my phone or on my laptop … it also seems like changing the port sometimes causes Plex to freeze. Doesn’t happen every time but when it does, it’ll be inaccessible for about a minute.
I am having the exact same issue, with the same PMS version on ubuntu 20.04. Remote Access will be enabled and work for 30 seconds and then red check mark and it is not working anymore…
You are right it is actually “working” as an indirect connection. It was working flawlessly until these past 2 BETA releases. I am not able to see my port opened at canyouseeme.org which is odd
No, the port is not open … I have other servers that are open and working just fine though. Seems to be something with Plex … I posted logs though and am open to the idea that I could be wrong but not sure where to look.
Already combed over that guide a thousand times. I’m a network admin so am quite familiar with the usual firewall/NAT/server access troubleshooting steps.
ERROR - [EventSourceClient/pubsub/172.105.96.32:443] MyPlex: mapping failed due to potential double NAT configuration
I also see a lot of this. This may not be related but it looks like a problem someone is going to have to look into for you
ERROR - [CreditsDetectionManager] BufferingLineReader: failed to read line (error: -1)
Mar 17, 2023 04:24:20.004 [0x7fd891aacb38] ERROR - [CreditsDetectionManager] BufferingLineReader: failed to read line (error: -1)
Mar 17, 2023 04:24:31.426 [0x7fd891aacb38] ERROR - [CreditsDetectionManager] BufferingLineReader: failed to read line (error: -1)
Update, apparently on my router my entry for Plex port forwarding was erased for some reason. I re-entered it, restarted my server and it is now working, for now…
My network is 172.16.1.0/24 and it’s successfully mapping the UPNP.
That port seems to be HTTPS and I don’t have HTTPS required or enabled.
That last one seems to be happening all over the place these days. I’ve got it set on a schedule to detect credits but looks like Plex’s credits detection feature still has some bugs.
Please turn DEBUG logging back on. There’s no space saved by turning it off. With it off, debugging these type issues is profoundly more difficult.
It does look your real ISP is somewhere in the Comcast system
Plex.tv does see your LAN IP as published on your 172.16.x.x LAN
Your Logs show me that your PMS system is connected to a router which has a WAN port IP address different than that of the ISP which connects you to Plex
Mar 17, 2023 03:42:21.238 [0x7fd893af0b38] WARN - [EventSourceClient/pubsub/172.105.96.32:443] MyPlex: attempted a reachability check but we're not yet mapped.
Mar 17, 2023 03:42:32.790 [0x7fd88fce4b38] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Mar 17, 2023 03:42:41.249 [0x7fd893af0b38] ERROR - [EventSourceClient/pubsub/172.105.96.32:443] MyPlex: mapping failed due to potential double NAT configuration
There is indeed double NAT here somewhere.
Your machine at 172.16.1.252
A router at 172.105.96.32 (your logs)
The real IP which connects to Plex.tv (what I see at Plex.tv)
Does this help?
Regarding another point in your logs I see.
Mar 17, 2023 03:49:46.279 [0x7fd88fce4b38] WARN - Overzealous client asked for end range of 442367, content size is 239512; we'll clip.
Mar 17, 2023 03:50:04.159 [0x7fd891aacb38] WARN - SLOW QUERY: It took 460.000000 ms to retrieve 1 items.
Mar 17, 2023 03:51:04.323 [0x7fd891aacb38] WARN - SLOW QUERY: It took 390.000000 ms to retrieve 1 items.
Mar 17, 2023 03:52:27.973 [0x7fd88fce4b38] WARN - Overzealous client asked for end range of 770047, content size is 396116; we'll clip.
The SLOW QUERY is a concern. It’s occurring many places in the logs.
Did you recently / are you still adding a bunch of new media into PMS ?
Mar 17, 2023 07:47:02.690 [0x7fd88ce61b38] WARN - SLOW QUERY: It took 4900.000000 ms to retrieve 4 items.
Mar 17, 2023 07:47:04.870 [0x7fd88ce61b38] WARN - SLOW QUERY: It took 2130.000000 ms to retrieve 4 items.
that’s 4 seconds to retrieve 4 items when it should be less than 1 millisecond
Hey there. Thanks for the quick reply. I’m scratching my head big time on this one.
Debug logging is turned on. I have plenty of space so not too concerned (yet anyway) with Plex’s use of space.
No idea what that IP is … I’ve done a network scan and nothing is coming up at that IP. The entire network is at 172.16.1.0/24 with nothing else in between.
Only thing I wonder is if the modem is somehow throwing in its own IP but even then, that’s supposed to be at 192.168.100.1 and I have it set in bridge mode.
How does Plex get this IP address? What can I do to track that done? I’m on Linux and Windows so can check from either.
I checked my OPNsense firewall and confirmed that it is properly allowing the traffic incoming on those ports.
I’ve got an Ubiquiti switch but there doesn’t appear to be any firewall settings on it.
What’s interesting is that if I ping that address from my other local machines, they can’t reach it … ping it from the one that the Plex server is on and “sendmsg: Operation not permitted.”
I attached additional logs again.
The other error I’d love to tackle once I get this external access sorted. I’m brand new to Plex (maybe using it for two weeks) and this is a brand new install that I got in place on Ubuntu Server about three days ago. Everything on it is running fine though … except when I click the test for Remote Access, it locks up.
There’s no Docker containers installed and no daemon for it either.
I do have Mullvad as a VPN running on here but a split tunnel has it sitting outside of that … and that network is a 10. network anyway. If I disconnect from Mullvad, it doesn’t make a difference.
IPv6 is disabled; I have it set to only use the network GbE interface that connects it to the switch.
Not sure if that was a post intended for me or not. This isn’t on a QNAP NAS … it’s on an Ubuntu Server-installed server.
Seems that IP may be associated with Mullvad as the command is dropped when traceroute/ping through their interface but it’s not found when checking through the tunnel.
Almost wonder if I should pop Plex onto a different machine or maybe toss the programs I use through the VPN into a Docker container or VM.
Not sure if that was a post intended for me or not. This isn’t on a QNAP NAS … it’s on an Ubuntu Server-installed server.
That said, I’m thinking it’s something on this box that seems to be blocking things … if I forward that port from the firewall to another box I have, all is well.
I’ve closed the port.
I think it might be Mullvad doing something it shouldn’t despite the split-tunnel being in place. Going to try something.
Looks like Mullvad, despite excluding outgoing traffic from Plex, was still catching incoming traffic and blocking it. I was able to create a new rule.
In a terminal session:
$ nano rules
Add this:
table inet excludeTraffic {
chain allowIncoming {
type filter hook input priority -100; policy accept;
tcp dport 32400 ct mark set 0x00000f41 meta mark set 0x6d6f6c65;
}
chain allowOutgoing {
type route hook output priority -100; policy accept;
tcp sport 32400 ct mark set 0x00000f41 meta mark set 0x6d6f6c65;
}
}
$ sudo nft -f rules
Re-opened the NAT on the firewall to test and it connected INSTANTLY.
No worries. I’ve been there myself and surely will be there again. Haha.
The entire LAN is wide open to itself … but everything coming from the WAN is blocked. The rules are in place to allow outside world to access designated hosts and their services on the LAN. Unless I’m understanding you wrong…?
I did have all ports from the WAN closed as I was going to use a VPN to remotely get into Plex but then realized the fam who wants to access it would never be able to figure that out so the less secure way of opening Plex to the world is the option (unless there’s something that’s more secure without removing the convenience of family just opening Plex and connecting).
Appreciate the help. I think having someone to just talk it through with made a huge difference … something that when I tried with the guys I work with was way over their heads. lol
