I know this topic has been brought up multiple times but I want to bring it up again as it becomes more and more relevant as many internet providers in the EU provide IPv6 only with IPv4 via shared GCNAT (which they do not allow to forward through).
Server IPv6
Allow the Plex server to advertise its public ipv6 address instead of IPv4. In this example my server has a dedicated IPv6 address, is publicly reachable but plex still says it isn’t reachable because it’s only using IPv4. Ideally you can also specify a domain that is used for external access (and if that domain is only an AAAA record you know it’s IPv6 only)
I’m using this setup for many years now, but mostly using the web UI by manually opening it using a custom domain with tls certificates configured for the plex server.
External Clients
(Specifically Sonos). To my understanding they receive the “public IP” of the plex server and connect to it. In my case this is the GCNAT ipv4 address from the screenshot, which causes the connection to go outside of the network, to the plex proxy and back. Making playback super unreliable. I don’t know the implementation details of Sonos, but 2 Points would be great:
-
- Similar to the first point, provide Sonos the IPv6 address of the server (which doesn’t even need loopback nat anymore in case of IPv6).
-
- In addition provide the local IP as well (assuming Sonos can try multiple destinations)
Business Case
I know Plex is a company, spending resources on implementing this might seem not really high priority, but supporting IPv6 natively would bring down plex-proxy traffic, thus saving money. Not sure if you have statistics how many clients this would affect, but my assumption is it’s a relatively large number in the EU (not sure how the US internet provider situation is)
Please think about it. I would also be happy to sponsor this feature if required.
