I have the question somewhere else and @pshanew referred me to this string.
the IPv6 stops at my router because my ISP only offers 64 bit prefix which is not supported by many devices including my Nvidia shield and Google WiFi Mesh. Is it possible to use the IPv6 address of the router then use port forwarding t reach my PMS?
where do I find the Plex generated Link to my server to adjust it to the IPv6 address?
I am guessing it only works with Static IP address. but are the dynamic DNS and certificate already provided by Plex also static? or do they update regularly ?
A 64-bit prefix is a standard delegation for a single subnet, is a ubiquitous minimum subnet size among residential ISPs, and is certainly supported by devices that support IPv6 like Google WiFi and nVidia Shield, so I’m not sure what issue you might actually be dealing with. One thought is that your firewall rules might block inbound IPv6 access to your server’s IPv6 address. You will need to add a rule on your firewall’s public interface to allow from any to your server’s IPv6 address on TCP port 32400, if you don’t already have that. The procedure and terms for this depend on your equipment. Another thought is that you might have multiple routers somehow, which would make sense if your Google WiFi equipment and your ISP’s equipment are both in router mode. You want one or the other, not both. That’s not really a Plex problem to solve.
It would not work to try to forward a port from the router’s IP address. That’s not the approach you want to take. Your server’s “internal” IP address is, in fact, a “public” IP address. There is no port forwarding to do. All you need is to configure the firewall rules to pass the traffic.
Review the notes above (Ipv6 support for myplex) and my comments on some of the subsequent questions for details on how to create the IPv6 URL for your server. You will need the IPv6 address of your server, which you can get by running ifconfig or similar on your server. You will then need to scrape your server’s key from the source html in the plex web app, which you can do in any web browser. You then string it all together as described above to craft the URL.
It works with static (manually-assigned) or “dynamic” (SLAAC or DHCPv6) addresses just the same. The certificate is a wildcard for all hosts using your server key, so it doesn’t matter specifically what IP address you use. Plex also handles updating the certificate, so you have nothing to worry about there.
I suspect you need to sort out the topology of your network. I think your firewall might be blocking inbound access to your server’s IP address, or, if your server doesn’t have an IP address, that might be because your ISP’s equipment is giving your Google WiFi equipment an IP address rather than delegating a subnet, in which case you need to put either your ISP device or your Google WiFi equipment into bridge mode.
Or else it’s evil gnomes, and there’s nothing to be done about that.
1 Like
Your avatar pic is 50% beard, and you’re preaching tolerance for evil gnomes? Suspicious…
@thornrag is absolutely correct. IPv6 is supported on Nest WiFi (just not on guest network) and by Nvidia Shield.
The ISP router should be set on Bridge Mode to be able to pass on the IPv6 prefix to Nest WiFi and this can only be done through customer service. Once that is done, I had to DISABLE it in the Nest network, close the app and restart the network then enable it again. then wait around an hour (or longer!) for the devices to be assigned an address. This is probably caused by a bug somewhere. The ISP however (at least in Germany) usually give dynamic IP addresses by default for security reasons ( so the IPv6 as well as the IPv4 addresses are likely to change).
If and when your server’s IP address changes, you will have to update it in your custom URL. Ideally, it will change only rarely. Glad you got it figured out!
1 Like
How can it be that we still have no proper IPv6 support in 2021, plus, how hard can it be? More and more customers are being switched over to IPv6, and it’s just a hassle to set it up.
Is there any official comment about why they still did not do this?
+1
En France chez SFR on passe en IPV6+IPV4 CGNAT
Please do IPV6 for Plex
I just have found the good T-Mobile home internet review. Kindly check and recommend!
With this method can you have a remote access with IOS app ?
I got switched to ipv6 only by my provider last week (just a shared DS Lite ip4 address, not usable for remotely accessing my LAN). Since then, it’s not possible to access my Plex server anymore from outside.
I just hope Plex is able to solve this and gets the PMS running on ipv6 only. Else, this will become an increasing problem with server owners, since more and more providers don’t provide static ipv4 addresses anymore.
You don’t need a static IPv4 address (just a public IPv4 address), and IPv6 works just fine for MyPlex. It is just MUCH more complicated to setup because there isn’t any NAT at the router with IPv6 you have to allow traffic to the IPv6 address of your server instead of setting up port forwarding. You also need to setup dynamic DNS.
So, how do you set up MyPlex on a DS-Lite type ISP link, without the need for 3rd party services (i.e. just modifying the router configuration). If this is possible, then this is a non-issue (once documented).
1 Like
I believe MyPlex requires a public IP, either IPv4 or IPv6.
I have a public ipv6 ip address, but that doesn’t solve the problem as described multiple times above in this thread. The only solution right now is to statically connect my PMS by entering the current ipv6 address url with plex direct. But this is not a solution compared to the automatic ipv4 behaviour, since public provider addresses can and will change more or less frequently. So saying that ipv6 works “just fine” with MyPlex is wrong. It does not.
If you have that much working you are close. You have to do the following:
Create a dynamic DNS entry using a service like afraid.org.
Put your new dynamic DNS FQDN in “Custom server access URLs”
That’s still the same problem of changing public ipv6 addresses. I have no service in my router or on my NAS that would update my ipv6 address at any dyn dns like service. My router only supports ipv4 dynamic dns. I’m not even sure if this makes sense with ipv6, since every device behind my public ipv6 prefix has a different ipv6 address. I would have to create a dyn dns entry for every single device I’d like to reach from outside. But as I just said, that still doesn’t matter, because I have no service at hand that automatically updates my public ipv6 address for a particular device.
With the help of a friend who is a professional server administrator I solved the problem with a VPN workaround by setting up a cheap cloud server (3 bucks / month) with an OpenVPN server, connecting to it through the OpenVPN service of my NAS (which runs my PMS) and tunneling ipv4 requests directly to my NAS. The PMS is correctly recognizing the cloud servers ip4 address as public PMS address and communicating it to MyPlex. No need for any custom config in the PMS. This way I have also solved the problem of Plex ipv4-only clients.
The cloud server has a 20 TB monthly traffic limit, which will do just fine for my PMS. The CPU load is about 10% per Plex stream, which is also fine for my use case.
Look around afraid.org, they have multiple ways to do dynamic updates; programs, scripts, etc.
IPv6 prefix delegations tend to be extremely sticky, I doubt it would change until you change routers. This depends on the ISP of course.
Hoping that my public IP doesn’t change: sorry, but I don’t consider that a solution. Else this whole thread would make no sense. At it’s core it’s actually about MyPlex providing the same functionality for public ipv6 addresses as it does for ipv4. Everything else have been work-arounds that hardly provide the same level of comfort or even functionality.
As a matter of fact, my IPv6 prefix changes at least once per day and I too have been switched to DS-Lite late last year. After some complaining to my ISP (not having had enough notice to prepare) I have been switched back to the previous setup, but its on borrowed time as I have been told that by the end of this year, they’ll switch me back onto DS-Lite for good, unless I want to pay them extra to retain an IPv4 address of my own.
Well, I can’t add anything to that except DS-Lite sucks. If it is changing that often, you really have no hope of hosting any services over IPv6, which may be the point. Every time the prefix changes, any active streaming would blow up.
