You do not have inbound IPv6 capability in spite of what might be stated.
What does “CanYouSeeMe.org” show for your IPv6 address ?
(you might need turn off IPv4 temporarily in the host to test this)
From my Smartphone I cannot access this URL.
I tried IPv6-Test.com. It shows IPv6 a native.
Screenshot removed
Now for the “not so much fun part”.
Sign into the modem and make certain IPv6 port forwarding is enabled.
In the switch over, any ports which you might have had for IPv4 may not have automatically copied to IPv6
Some (I think most) Fritzbox have the option to enable IPv6 being passed in. You will need this as well if it’s an option.
Port 32400 is open for IPv6 for the Raspberry.
I can also reach it from the Internet with the raspberry’s IPv6 and port 32400
Screenshot removed
Edit: Direct connection of clients is working correctly, when I enter the abovementioned alternative URL. So I think my router and port forwarding are configured correctly. When I do not provide the alternative URL and leave this field empty, then the connection doesnˋt establish correctly (without channging any router or port forward settings). So I think, that some IPv6 detection in the PMS- or client/app-software isnˋt working properly.
thank you… That covers what I needed to see.
At this point, our final step is to see, or did you already,
- see if you can connect via Plex/web (app.plex.tv) in the phone browser
- with WiFi turned off
I just tried it with no alternative URL there seems to be no problem. Connection in app.Plex.tv is shown as direct as you can see on the attached screenshot.
But playback is starting with a large delay of about 20-40 seconds and it only let me choose transcoding with max. 2 mbps. From other Plex servers I can also play with original bandwidth.
Below you will find the logs from app.Plex.tv from my iPhone with WiFi turned off.
Log removed
Edit: I removed all the old logs as well as the screenshots because of privacy reasons. And I will also delete the above log, when you downloaded it. As I saw a lot of information regarding my libraries, email-address, IP-addresses etc. are stored in clear text in the logs and I don‘t want the whole world to see all this data stored in the logs. Isn‘t there a more non-public way to share the logs with you?
I’m sorry I didn’t get to your logs before removed. It’s been a VERY busy morning.
Is there ANY way you can work with the ISP support staff to get an IPv6 port forwarded through your modem to come out onto your LAN as IPv4?
I fear the only alternative would be to migrate entirely to IPv6.
@Volts Do you have any thoughts here?
I could send the logs to you via direct message or via email.
The IPv4 „thing“ is not possible with my ISP. I was also asking for PCP support which is also not possible.
Deactivating IPv4 is not an option at this Moment.
For now the current solution with the Plex direct URL is working for me.
Well, if it’s working that’s most important.
Might there be a way to have PMS use an IPv6-only adapter on your machine (as the primary adapter) and maintain another adapter as the IPv4-only for communication with rest of the LAN ?
It would give you duality while allowing IPv6 inbound, wouldn’t it?
Well, I could of course try this. But I think this is beyond my networking abilities and far above the level of my Linux skills 
What I would do, presuming you have the hardware in the machine.
-
Leave your current main ethernet adapter as is to support your LAN
a. IP v4: ON
b. IP v6: OFF -
Plug in the cable to the second adapter then, in network settings (for Linux)
a. IP v4: OFF
b. IP v6: ON
The last change is dependent on the devices in your home.
Do they also speak IPv6 / IPv4 or are there any limitations?
It’s a raspberry pi 4 with only 1 LAN adapter.
So I will use it with the .Plex.device workaround.
Yes. afraid so.
It’s been a while since I created this thread. Since others have posted too, just wanted to update that I never was able to get Plex to work with IPv6 and gave up after spending a lot of time on it. I agree with others that this issue needs to be fixed so that it doesn’t involve such complex number of steps to get it working, maybe.
My solution was to switch to Emby. Of course, Emby had it’s own string of issues that took days to resolve, but remarkably, their IPv6 solution works out of the box. If Emby can do it, I’m sure Plex can do it. However, Emby does have a list of issues that doesn’t make it preferable to Plex. Sometimes videos won’t play for unclear reasons. So for now I use both Plex and Emby in parallel, in a sort of limbo until I figure out what to do.
Finally, a major spoiler alert for those using Plex with Roku TV, as I do. Roku does NOT support IPv6. After all the troubleshooting and running Emby in parallel I found out that Roku will not allow IPv6 access anyway, despite Emby being IPv6 compatibke. So the limitation is to use web or mobile access. If you’re trying to share your collection with family members using Roku TV, it doesn’t seem like it’s going to happen. There has been a popular feature request submitted to Roku for many years now, but they have not budged either. It’s a bit incredible for companies like Roku and Plex to not support IPv6 when ISPs have already began the switch.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
