Hahahah, sorry, I wasn’t clear.
I mean that there’s “no” issue, because there are only about 5 people with manually-configured iPv6 servers. Plex doesn’t support it automatically. So it doesn’t come up as a support topic.
I 100% agree that it doesn’t work.
Ah I see! 
I suspect there are a lot more than 5. I also suspect mine doesn’t count as I block all/most telemetry URLs at the network level (firewalls, DNS, the works).
In any case, I suspect there’s a lot of hidden demand for this. I’ve been waiting for about 2 years to get my server on IPv6 and just recently found this manual workaround. Until now I’ve been relying on VPNs and designated myself to watching on computer or tablet as I couldn’t ever watch on a smart TV.
I never contacted support because just by reading the docs and forums it was clear it wouldn’t work.
Yeah there’s bit of a black hole in the support, there’s just no clear documentation “what do I do if I’m on IPv6?”.
At this point there are a few options for the growing number of people with IPv6 + CG-NATed IPv4 home connections (aka DS-Lite, 464XLAT, etc):
Using IPv6:
*.plex.direct URL + manually configured firewall traversalplex.yourdomain.com + manually configured firewall traversalUsing IPv4:
Indeed.
These are all incomplete options at best though.
IPv6 1: manual work, may break if PD changes (why an ISP would inflict that on their customers is behind me but apparently some do).
IPv6 2 Costly, requires extra infrastructure and tech knowledge, may not work everywhere.
IPv4 1 I do that. Doesn’t help on devices where you can’t run the clients, or the other cases you cited.
IPv4 2 Costly, slow and/or otherwise clumsy and error-prone.
There are options but none of them are actually good.
Yeah, the real solution is for Plex to implement what it already does on IPv4:
*.plex.direct URL automatically and uses PCP and/or UPnP-IGDv2 to open port 32400 in the firewall automaticallyBut that’s what this whole thread is about, the feature request for exactly that. 8 years and counting 
Do you have any sense of how well PCP (or UPnP-IGDv2) is supported on CPE routers/firewalls?
I’ve seen some that do - problem is it’s rarely advertised (saying the router does “UPnP” doesn’t really imply if it does only v4 port forwarding or also v6 firewall traversal). But RFC8585 at least specifies all CPE should support it.
There’s been improvement in AWS’s support for IPv6.
If that was previously a barrier to this feature, I wonder if it could be reexamined.
Nah… lets wait another 8 years to be ipv6 fully implemented.
hi,
my french isp SFR change my full ipv4 connexion to a full ipv6 + IPV4 CGNAT , with many difficult change it work (AAAA DNS, remote connect) but not like before… could you put a full support of IPV6 for plex ?
+1 vote
US here. ISP just updated to DualStack Light. Unwiling to give out a public IPv4 as “IPv6 is natively public so you shouldn’t need one”.
Remote Plex no longer works.
Cancelling my PlexPass subscription; no point in keeping it if I can’t even access my content outside of my home network. Might as well just watch the MP4s directly.
Disappointed. Now looking into alternatives.
Check this
It’s so sad that Plex has not provided full ipv6 support in almost 2022.
What about emby or jellyfin?
The direct link workaround works well if your IPv6 PD doesn’t change – you set it up once and from that point on it just works, as long as the client side also supports IPv6.
Some weird ISPs make the PD dynamic though, so watch out. From what I’ve been reading around, it’s especially common for US ISPs to do that, despite not having any good reason to do so. It’s plain user hostile behaviour IMO.
In any case, back to Plex. It is pretty sad that this is not officially supported and that it requires manual wrangling on the part of the user. It does work though.
I have a static /56 with my provider, and they do DHCPv6-PD out of that & give me a /59…which is useless as then I have to renumber everything any time it changs (which could be a cable modem reboot).
So I’m now running a 6in4 tunnel to have static ipv6. The native ipv6 support is horrible & nobody in support can help me & I have no other ISP choices.
I really wish plex supported ipv6 fully. I already have a friend who I’m running a Minecraft server for that only has full speed internet on ipv6. He has trouble connecting to ipv4 stuff at any decent speed (I think it’s limited to 1-10Mbit/s per user based on time of day - university setting. V6 fixes it).
FYI - I use the IPv6 method from the above article to get external access working from my CGNAT Starlink internet connection and this has working fine for a while now, however when i recently upgraded to the latest version of Plex (Version 1.25.4.5426) this stopped it from working and i had to downgrade back to Version 1.25.3.5409 which got me working again. Might be helpful for others having the same issue.
Ideally Plex need to make IPv6 part of the Remote Access section like IPv4 is.
Making this happen would probably substantially reduce the load on their servers from all of the people being forced to use Relay due to CGNAT and not willing to deal with some janky workaround. IPv6 isn’t even the future, it’s been around since the early 2000s. ISPs and services like Plex just need to make it universal.
iOS and tvOS apps were updated in September to “Support IPv6 server addresses”
And indeed, if you add “includeIPv6=1” to an authenticated request to https://plex.tv/api/resources, if a server is properly configured for IPv6, you should see an IPv6 address along side IPv4 addresses:
<Connection protocol="http" address="2607:5300:de:ad:be:ef" port="32400" uri="http://[2607:5300:de:ad:be:ef]:32400" local="0"/>
So it looks to me like work is being done here, and with the right combination of server and client support, IPv6 remote access is working (I can confirm I see this in practice from Apple clients).
Yep… works for Apple clients even on a pure IPv6 environment. Though the remote access status indicator in Plex Web will show remote access to be „not working“. So hopefully this is more a question of WHEN than IF other platforms will be supported (fingers crossed)
Apple requires all apps must work in ipv6 only environment. Even my washing machine supports ipv6. 
Plex clients like iOS/iPadOS/tvOS have for many years worked with IPv6 (using custom server URLs), it’s IPv6 Plex servers that (until recently) had to be set up manually.
So it looks to me like work is being done here, and with the right combination of server and client support, IPv6 remote access is working
This is great news, and hopefully will lower the flood of “help I am behind CG-NAT” questions. At the moment ~50% of the internet users in the US, Germany, France, etc are on IPv6, we’re well past the point where out-of-the-box IPv6 support is a “nice for the future” feature.
Does PMS actually support PCP or UPnP-IGDv2 to open IPv6 firewall ports? That’s the last ingredient to make IPv6 support as seamless as IPv4, where this is done with UPnP-IGD (or NAT-PMP?).
