Server Version#: 1.25.6.5545
Player Version#: 4.69.1
So I have a server which is in a Datacenter - so there’s no NAT, NAT64 etc, it’s got both IPv4 and IPv6 as public IP’s.
No matter what combination I try of custom server URL in Settings → Network, I cannot get the streams to work via IPv6, they’re always via IPv4. Nearly EVERYTHING else is v6, but the websockets aren’t as show in this IPFoo output:
I have added the custom URL as https://xxxx-xxxx…serverid:32400/web as in a number of other threads, but my sockets are always v4. All of my devices are getting Disney+/YouTube via v6, so I know the house is working correct.
Yes - it’s in a datacenter, so it has an 100% static IP. Fully routable, available, I can get to it from my connection and DNS AAAA record has been added. Have done a port scan from an IPv6 host and port is open.
Yes I understand, but as I’m the network engineer I know it’s ipv6 It’s dual stacked with a v4 and v6 static - as it’s in a DC there’s no DHCPv6/SLAAC or RDNS, it’s all 100% manual (but definitely v6)
Purely for my own use and testing - it’s just so I can use a hostname, but it doesn’t change anything to do with plex, just the certs I use for the UI, which are LE (but require a hostname).
We know that Plex is particular about IPv4 address ranges, and I noticed that it doesn’t register IPv6 link-local addresses. That’s why I’m curious if you’re using addresses from the official GUA range.
I’m curious. What happens if you set Settings → Network → Custom server access URLs like this?
http://[colon:separated:ip:v6:ip:addr:like:this]:32400
Note: Include the square brackets.
Is it then published, using @Volts directions above to test? On my own server I can publish valid IPv6 addresses in this manner (though mine works using Plex’s automatic detection as well).
If that works, it’s likely that Plex’s servers are unable to detect your IPv6 address for some reason.
AFAIK the Plex Media Server identifies its own IPv6 GUA and ULA addresses and publishes them.
Or if you manually enter an address (in the format you describe) that’s immediately published.
I don’t see any “detection” of IPv6 from the Plex cloud servers, or any reachability testing from the Plex cloud. It doesn’t use the same mechanisms as Remote Access does for IPv4.
The ULA address mine auto-publishes isn’t reachable remotely. And I can publish random not-mine or not-reachable IPv6 addresses.
Yep, I was unsure about this myself; I may have used “detection” a little loosely there. Since this topic has warmed up again lately I’ve been planning to perform some testing to gain a little more knowledge of how it works.
Okay results are getting weird, but I’ve gotten one result to work.
If I go to the URL of the server direct: (https://[xxx.xx.xx]:32400, it tries to redirect me to app.plex.tv and is unable to complete the request.
It then redirects to plex.tv - I click Open App and it opens my server through apps.plex.tv and lo and behold - there is an IPv6 entry for plex.direct. I play content and it’s using the ipv6 websocket.
It’s dual stacked with a v4 and v6 static - as it’s in a DC there’s no DHCPv6/SLAAC or RDNS, it’s all 100% manual (but definitely v6)
Let me know if you see anything different from what I’m seeing! Please look at my comments 
