PLEX NEEDS TO DO SOMETHING ABOUT IT NOW!
instead of wasting resources and time in those crappy movies integration, they should help with ipv6!!!
4 Likes
I have no clue why it can be that hard for Plex to support IPv6…
It should be standard nowadays as IPv4 prices are rising and with IPv6 you can do anything.
Sorry for the late reply. I found out that it worked. I had to enable unsecure connections first. So that it works. But I also asked my provider for Dualstack and got a real ipv4 and now it works without a problem with my domain and over plex.tv. However, I would have preferred that ipv6 would work more easily like the ipv4 way…
Here is how I configured my plex:
When you then connection over your dyndns or ipv6 where the plex server is available it should redirect you first to plex.tv for logging in and then it says something like it does not support unsecure connections but if you deactivate it you may establish a connection.
Yeah for a server it’s better at this point to have it on dual stack if you can get it, as you cannot serve IPv4-only clients from an IPv6-only server. But public IPv4 addresses are rapidly disappearing from residential connections, so dual stack isn’t an option for everyone.
If it only works with the settings on “allow insecure connections”, that means your certificate isn’t correct, or Plex fails to pick it up correctly.
Why in the hell plex does not appear to bind to [::]:32400 as in all interfaces, IPv6/IPv4?
man in times like these i would love to share my library with my family but stupid ipv6 is not supported…
1 Like
IPv6 does work, but you have to set it up manually with a custom server URL and a certificate. Not ideal but better than nothing.
Custom domain and certificate not strictly necessary. You can use the dynamic DNS and certificate already provided by Plex.
Plex generates a custom URL for your server in the plex.direct domain. You can copy that URL, modify it to point to your IPv6 address instead of your IPv4 address, and then use the result as your “Custom Server Access URL.”
It would look like this:
https://ABCD-1234-ABCD-1234-ABCD-1234-ABCD-1234.0123456789abcdef0123456789abcdef.plex.direct:32400/web
- Get your IPv6 address, make it all uppercase, and replace the colons with dashes.
- To get your server ID, load a video, inspect an element, and look in the Network tab for a resource that has a
<IPv4 address>.<server-id>.plex.directURL. The<server-id>is a 32-character hexadecimal string that identifies your server.
Plex has done everything they need to do to support IPv6 remotely, it seems, except to start generating and serving AAAA records for their plex.direct URLs. I can’t imagine what the hangup is.
12 Likes
Is Plex smart enough to pick the static ipv6 address or will it pick a dynamic (PE) address for that URL?
You pick it. The hostname reflects the IP address; it resolves to the IP address encoded into the hostname. If you want to use a particular static IPv6 address, then make that IPv6 address all uppercase, change the colons to dashes — also, you can’t collapse zeroes, you have to put every digit — and then use that.
I mean, most systems auto-configure at least two routable IPv6 addresses through SLAAC, a static one and a dynamic PE one (typically 24h ttl). Is Plex intelligent enough to take the static one to convert to the DNS name?
That is all true, but it doesn’t affect this hack. Plex is doing DNS trickery, not actual dynamic DNS.
The DNS server for plex.direct is simply decoding the host portion of your query and returning that as the IP address. Anything you put as the host, if it’s a valid IP address, will be returned as the IP address. It can be literally any IP address. dig -A 8-8-8-8.<server-id>.plex.direct and the result will be an A record for 8.8.8.8. dig -A DEAD-BEEF-DEAD-BEEF-DEAD-BEEF-DEAD-BEEF.<server-id>.plex.direct and the result is an AAAA record for dead:beef:dead:beef:dead:beef:dead:beef. These addresses are not pre-registered anywhere, dynamically or otherwise. The server is just converting the dash-encoded IP address in the query back into an IP address on the fly, and returning the result.
It has no idea whether the IP address even points to your server. It’s just mindlessly regurgitating your query in the form of an IP address.
So if you want Plex clients to access your Plex server via your Plex server’s static IP, then your Plex server’s static IP is what you encode into the plex.direct hostname for the custom URL. Simple as that. Whatever you encode into the hostname is what the hostname will resolve to.
Got it - excellent. Does the certificate get generated as a wildcard cert for all subdomains of *.[server-id].plex.direct ?
Exactly right.
Why doesn’t Plex push those [ipv6-address].[server-id].plex.direct URLs to the clients along with the IPv4-derived one?
+1
I need IPV6 support because my internet operator does not accept IPV4 anymore, and claims that I was obliged by the regulator to update to this new protocol that will become the new world standard.
My case is what the colleague mentioned “DS-Lite”.
There is no ping by IPV4 via the External IP. Totally inaccessible.
Plex can now manually be set up to work over ipv6 (see the posts above), but bear in mind that in order for this to work, your clients also need to have ipv6.
If for example your mobile carrier has not switched to ipv6 yet, you cannot access your ipv6 server from your 4G/5G phone.
1 Like
Thank you very much!
But, how do I configure manual IPV6? Because I read some topics that said it was necessary to register a domain to bridge the internet with the server’s local IP.
Registering your own domain isn’t necessary (anymore). A few messages above, post 269 from 20 days ago:
1 Like
