Ipv6 support for myplex

Don’t forget that in order to vote you need to “Like” the first post.

So many "+1"s in comments…

Another ISP whose subscribers won’t be able to share their Plex servers:
ispreview.co.uk/index.php/2016/09/uk-isp-hyperoptic-scraps-static-ip-shared-cgnat-internet-addresses.html (without paying an extra £5/mnth)

Going to try some of the workarounds listed in this thread, but would like native support! Added my vote to the first post.

@marc_ferna said:
I used @BNO2006 short guide on his signature PMS, PlexWeb and DS-Lite and I made it work! Here are the steps I followed:

1 - Create an account on MyOnlinePortal
2 - Once you are logged in go to the PortMapper section.
3 - Create a New Port Mapping. Choose a random port for the first field. Then your IPV6 address and then the Plex port (32400 by default)
(Remember you need to open the port in your router as well - I have an AirportExtreme so PM if you have any questions on how to set it up.)

4 - Finally, go to your Plex Network settings, and add the MyOnlinePortal url for the Custom server access URLs - remember to add ‘/web’ ad the end! Should look like this:
http://portmapper.myonlineportal.net:<RANDOM_PORT_CHOSEN>/web

Let me know if you have any questions

Thanks for this, @marc_ferna! I also have webpass and this seems to work even though I still have the red exclamation mark next to my remote access settings. But this gives me an “indirect connection” to my server, is that correct?

+1 needed for the future

plex direct links could be simply 2001_0db8_0000_0010_9875_6f51_ca6c_7e47.133790016815abeabeface13379001ab.plex.direct

@Aetherous said:
+1 needed for the future

plex direct links could be simply 2001_0db8_0000_0010_9875_6f51_ca6c_7e47.133790016815abeabeface13379001ab.plex.direct

Could work reasonably well if the Plex Server could detect which is the normal IPv6 the NIC has and not use some temporary address used because of the privacy extensions. I know there are ways to do so in Linux at least, no idea about other platforms.

Don’t know how useful this is but I got mine to work. I am currently in a situation in the US where my ISP appears to be using both IPV4 and IPV6 and Windows is starting to prefer IPV6. I use an Android device and in the client settings under Advanced/manual connections I specified my IPv4 address and it appears to be working for now

Windows has preferred IPv6 since XP when IPv6 was enabled in it and IPv6 was enabled by default since Vista.

Plex will not use IPv6 for anything automatically unless you use custom access URLs.

+1 for native IPv6 support, pretty please!!

+1 for native IPv6 support. BT just made my Plex Server unreachable.

Update: IPv6 is now working for me. The fix was to set a “pinhole” in IPv6 settings for the port I was using for remote access. BT allows pinholes to be defined in their settings for the Home HUB 6.

Lets push this topic to the top again. +1

@rkv said:
+1 for native IPv6 support. BT just made my Plex Server unreachable.

Update: IPv6 is now working for me. The fix was to set a “pinhole” in IPv6 settings for the port I was using for remote access. BT allows pinholes to be defined in their settings for the Home HUB 6.

Could you explain that in a little more detail maybe?

To my suprise plex over IPv6 is working when using network -> custom URLs. I have one domain pointed to my IPv6 adress and its streaming over Ipv6 without a problem. The Trick is just to disabled external access and only use the custom URLs. Some DYNDNS and myfritz services support updating both the ipv4 and ipv6 entry. If no connection can be made over ipv4 it will work over IPv6!

Please FULL IPv6 support please.

Has anyone figured out why indirect access sometimes works and sometimes doesn’t with DS Lite?

Also, I have an HTTP proxy set up (which technically allows outside access, but only over the web UI). If I set up the URL under “Network > Custom server access URLs” I would expect Plex to just pick it up (based on the explanation), but it seems that it’s only used for IP address resolution or something (which wouldn’t work, as the reverse proxy is domain name based), it doesn’t actually end up giving me a direct connection say from iOS or tvOS clients.

If you can access Plex Web via a url put that Url (including https and an http version for older clients) + port in custom access.

I.E. “https://plex.example.com:443, http://plex.example.com:80” removes "'s ofcourse. Port is required, if you don’t it adds the remote access port which may not be the same for hitting the proxy.

+1 yes please

Use the like button on the first post to add your count to the feature request

Or realize that it works just fine over IPv6 only. Unless you have no DNS/NAT64, which mean that 75% internet dosnt either, including this forum.

@Napsterbater said:
Or realize that it works just fine over IPv6 only. Unless you have no DNS/NAT64, which mean that 75% internet dosnt either, including this forum.

That’s the problem and why this thread exists. We need a solution for it!