Yeah it’s really weird, Plex has to be one of the last (non-legacy) applications left on earth where IPv6 connectivity is some sort of ‘special case’ instead of the default.
4 Likes
I need IPv6 support. Everything does support IPv6, my workspace, my mobile carrier, my home ISP but i don’t have public IPv4 and it is impossible to get without doing stupid ■■■■ like tunneling everything through the world.
2 Likes
The funny thing is, as ISP’s all over the world steadily continue transitioning their hundreds of millions of household connections to DS-Lite (and sell off their IPv4 blocks for $$), at some point the people at Plex are going to notice that the bandwidth bills for Plex Relay start ballooning because more and more servers are automatically tunnelling via Plex instead of connecting direct through IPv6.
3 Likes
With only 228 votes currently I don’t think that’s going to be anytime soon.
2 Likes
The vast majority of users are not network specialists, I’m pretty sure that 99% of the people who find out Plex doesn’t work on their DSL/cable/fibre line have no idea why. How many will notice they don’t have a direct connection and are tunnelled? Of those, how many realise it’s because of missing IPv6 support? How many of those take the effort to go register on the forum to vote in this topic?
Every Tom Dick and Harry will notice Plex doesn’t do Carplay though, and it’s an easy skip to the forum to ask for it. Carplay, speed control for video playback, unskippable custom pre-rolls or Alexa support are indeed nice additional features, but missing IPv6 support actively prevents tens (hundreds by now?) of millions of potential users from using Plex at all, and annoys the hell out of the existing users who had it all working over IPv4, and find out that after the transition all software developed in this decade works except Plex.
10 Likes
+1
Whoever’s responsible for product features prioritization, please GO AWAY and replace him with someone capable who doesn’t think that hosting media on S3 is more important than easy remote access through IPv6.
1 Like
+1 I would need this feature because of ISP CGNAT
IPv6 is coming in a big way. The fact that Plex can not use it is a horrible mistake. In particular, our house will switch from Comcast, to Starlink, next year. I can not imagine that Starlink will offer any IPv4 access, other than maybe via CGNAT.
IPv6 solves so many issues, so nicely.
I hate to agree with this, but at this point, most applications from the last 10 years are IPv6 based.
Better to switch over now, and be able to offer more passes around the globe.
Its annoying waiting so long for such a mandatory function.
1 Like
That’s basically it: We need reworked “Remote Access” settings where you could enter a dns name instead of an IP and the functionalty to let this work with IPv6 AAAA records. Then everything is fine and I could finally use my Plex Server from everywhere. For now I am bound to my LAN.
2 Likes
You can set a DNS name in custom server URL settings, like sub.domain.com:32400 and that will work. The problem is that you have to:
-
buy a domain name pointing to your server’s IPv6 address
-
buy a certificate for that domain to be able to do secure connections
Both these things are done automatically for IPv4 without any user knowledge or input (Plex generates a dynamic dns record & cert), but need to be obtained separately and installed manually for IPv6.
For now you can do it using a Dynamic DNS, but the streams will be using indirect connections. IPv6 support would be an awesome feature!
I don’t think that’s correct, if you use IPv6 through DDNS custom server URL’s you’re going direct, not tunneled through Plex.
2 Likes
+1 for this feature. ISP put me behind CGNAT so can’t connect direct on IPv4. I have native IPv6 from ISP.
Now that I tested it with Dynu you’re correct. I am getting direct connections
+1 no way out of CG-NAT for me too
@certuna what do I have to do?
- I activated under network ipv6 support.
- Added a custom certificate for my domain.
- Added my domain unter custom certificate domain.
- Activated Relay Server
- Added https://my.domain:port under custom server access url
However, Plex.tv still does not want to connect to my server. But gives the option to deactivate the Secured Connection to my Server to Connect to it.
Sometimes it works then and sometimes it does not.
I have DS-Lite and the IPv4 is CG-NATed
Honestly, I don’t know what happens exactly at the plex.tv remote end of things.
Can you connect through the browser if you put https://yourdomain.com:port ? I.e, bypassing the whole plex.tv thing
Well I am trying to install plex on my IPv6 only network, put it just does not work because of plex.tv unable to communicatie IPv6… Such a shame as I am gonna host this within a datacenter. At home I had a local PC with IPv4 and all went well but now with IPv6, it gave me headaches and I got pretty much demotivated to use Plex anymore…
