IPv6 (DS LITE) Remote Access?

Server Version#: latest plex pass
Player Version#: latest plex pass

Hello,

is it possible to gain remote access via IPv6 (DS LITE)? Don’t want to use port mapper, because that has a bad performance. Is there any other and better way?

Thanks!

Regrettably Plex doesn’t work (remotely) over IPv6 without a pretty major workaround: register a domain name + certificate, set up the AAAA record mapping your server’s IPv6 address to that domain name, install the certificate in Plex, and add the domain name as custom server address in all the clients.

Yes, it’s rediculous that it’s 2019 and Plex doesn’t work over IPv6 without hacks like this, but it is what it is. All I can say is, vote for this feature request: https://forums.plex.tv/t/ipv6-support-for-myplex/

In the big picture, it’s about 30-35% deployed.
https://www.google.com/intl/en/ipv6/statistics.html

Adding IPv6 support to networking based software isn’t as easy as folks think.

It’s not developed overnight I agree, but this problem has been flagged six years ago already, and over the past few years nearly all other networking software has been made to work over ipv6.

Now it’s 2019, IPv6 with either no or only CG-NATted IPv4 is getting rolled out to end users by the millions all over the world on both mobile and fixed lines, and the complaints are flooding in that everything works except Plex.

The “remote access” subforum is now full of complex workarounds (VPNs, ssh portforwards, ngix, own domain name/certificate, IPv4-tunnel services, etc), not to mention the German-language forum which was the one of the first big countries with large-scale IPv6-transition.

I mean, adding IPv6 support won’t solve all connection scenarios:

  • server on IPv4, client on IPv4: works
  • server on IPv4, client on IPv6: works
  • server on IPv6, client on IPv6: this should work by now, but Plex has dragged its feet here
  • server on IPv6, client on IPv4: will never work without some 3rd party (or Plex-hosted, like Relay) intermediate

This portion of how PMS works has nothing to do with IPv4 or V6. It has everything to do with Certificate, Public-facing IP handing and referrer. This is how they chose to implement it.

I’m not defending or supporting, I’m merely stating what is.

I know work to implement native V6 is ongoing.
When it will be done is unknown.

Manual custom server addresses/certificates are indeed the same for IPv4 and v6, but for v6 access it’s the only way to get access, while for v4 it’s for most users smoothly handled by default through myPlex and their dynamic DNS/certificates.

The whole reason why ‘suddenly’ so many users find themselves in a situation where they have to tunnel out is because they’ve lost their public IPv4 and now get a public IPv6 instead (and a private IPv4). They cant use incoming IPv4 anymore and Plex doesn’t use the IPv6 address where they are accessible.

I’m very happy to hear that native IPv6 support is now under development, just a bit frustrating that it’s only now being done instead of six years ago when this was already flagged as a big issue.

Moving to General Discussions because this is not platform specific.

This topic was automatically closed after 90 days. New replies are no longer allowed.