For me this just doesn’t work. I even have my own server online with static ipv4 and ipv6, i can route through them, but PMS still works very unreliable.
Did you setup the “Custom server access URLs” in the PMS network settings?
Yes I did.
Sorry for the late answer :o
Any news from the devs about when proper IPv6 support is going to be added?
I’ve tried many things. The workaround using the direct URL is very limited, I can only get an indirect connection on apps.
If I open the URL on the browser, I get a regular remote connection at full speed.
Some apps don’t even have the option of setting a custom server address, and some only take IPv4 addresses.
It’s 2021, we have run out of IPv4 addresses a few years ago and many of us can only get a direct connection to our servers over IPv6.
3 Likes
This thread already has 8 years and there’s no solution, if you’re behind a CGNAT you’re damned, pretty sad.
Did you see this message above?
This works quite well, assuming your clients and their networks also support IPv6.
Yep, saw it, implemented it. Works a treat if I connect to the direct URL via the browser. From the apps gets relayed and limited to 2mbps, even the Plex app on the same computer, so - yeah both ends support IPv6.
I think this is because the URL in that post has /web at the end of the link, if you remove that (so just https://[ip address-with-dashes].[server ID].plex.direct:[port], it works with the apps too.
Yeah I never added the /web at the end. Actually not true, I did at first but removed it as soon as I noticed it.
Funny enough, it looks like it’s working as expected now, at least from the Mac and iOS apps. It shows as remote streaming with my current IP instead of relaying. I’ll try the TV one later on but this is encouraging. Not sure what might have made it work, I haven’t made any changes on either side since the last test.
It’s still far from ideal to have to go this route. The remote config is useless under CGNAT (although I’ve read somewhere - maybe on this thread - that it needs to be enabled even though it doesn’t work).
I don’t get why they feel like they have to determine my IP automatically. Just let me type it in and I could even get in via a VPN port-forward without having to go out via the VPN unnecessarily.
Seeing how this actually seems to work, the fact that support is not built-in just reeks of either laziness or financial trouble. I suspect the latter given the recent focus on pushing crappy streaming content, Tidal integration, etc.
That usually isn’t possible. Stateful firewalls and NAT/NAPT devices expect to see both “in” and “out” legs of a TCP session. Competent ISPs and VPN providers won’t forward traffic that originates from foreign IP addresses.
Right. I could have been clearer.
It would still have a route out via the VPN in this case, but it wouldn’t be the default route - meaning it would still accept inbound connections within the LAN, and it wouldn’t have to go via the VPN for things like downloading metadata, subtitles, etc. whilst being accessible from remote locations via the VPN port-forward.
Ahh! I understand. I don’t think that’s directly related to IPv6 support for myplex, or how apparent-address discovery works. I wasn’t sure what you meant. 
It’s pretty unusual for an application to support split/policy routing like that.
For either IPv4 or IPv6, that could be accomplished with a Reverse Proxy behind the VPN, and excluding Plex from the VPN completely.
It’s “laziness” - this whole IPv6 issue has been flagged (checks start of this thread) eight years ago, Plex clearly have not been in “financial trouble” for all of that period. From what I’ve gathered over the years, the devs are not really comfortable with IPv6 and don’t use it themselves, so all these issues that immediately pop up with users on IPv6 connections are not understood or prioritized.
It’s not only the issue with URL construction - for example, mixing v6 and v4 ranges in the “allowed subnets without auth” for example isn’t possible, and I never got PMS to work on a single stack IPv6+DNS64 network.
I hope IPV6 get full support, it would be awesome!
1 Like
Yeah it would not even be that complex I think:
- extend the current support for UPnP-IGD and NAT-PMP (which do IPv4 port forwarding) to also do UPnP-IGDv2 and PCP (RFC6887) for IPv6 firewall traversal
- read the system’s stable GUA address and construct the correct URL to push to clients
2 Likes
That’s probably part of the challenge with IPv6. In some deployments the address will change quite regularly.
I think another part of the challenge is that nearly all clients will have some way to contact IPv4 servers. But some clients won’t have IPv6 capability. So an IPv6-only server won’t be reachable by some clients.
OK, but Plex currently has no problems with dynamic IPv4 addresses, handling a changed IPv6 prefix isn’t much different.
IPv4 clients will never be able to connect to an IPv6 server (except for Plex Relay) but that’s what it is, there’s nothing Plex can do to make IPv4 forwards compatible. But at least make it work for those with IPv6 servers and clients…
I kinda-agree. With real-world IPv4, addresses are pretty stable after an interface comes up. With IPv6 it’s just more likely, more often.
Or maybe I completely agree - maybe it would be easier for Plex. It already tries hard to detect router WAN IPv4 address changes; noticing a prefix change is a lot easier.
Yeah, I agree. It’s just a different kind of support request. Today there’s no issue with IPv4-only clients being unable to connect to IPv6 servers.
I think the suggestion of a premium $ enhanced relay offering is something Plex could consider.
Yeah, I guess the clients need to throw up a meaningful error message (“the server you are connecting to is IPv6, you don’t have that”), otherwise support will be flooded. Then again, the forum/subreddit is already flooded with “remote access doesn’t work”.
Plex Relay traffic will go through the roof over time as the majority of residential internet connections disappear behind CG-NAT (for IPv4), I wonder how long they’ll be able to offer that for free.
3 Likes
I’m not sure I understand what you mean. There’s definitely an issue with IPv4-only clients being unable to connect to IPv6 servers. In fact, there’s an issue with any client being unable to connect to IPv6 servers, unless you hack your way in by manually adding the direct URL in the network settings.
2 Likes
