Hello,
I have a problem with remote access.
I think it comes from IPV6, and the absence of NAT.
I have browsed the forum but without finding a real answer to my need, except here, but I have not yet looked into it.
Is there an official plex operating mode concerning IPV6?
If your ISP is using CGNAT, then you may need to contact them, to see if they can offer you a fixed IP address or a similar solution, otherwise Remote Access may not work for you.
And before you ask, it is out of Plex’s control.
You might possibly be able to use a VPN as a workaround, but that VPN would have to allow Plex to passthrough. Talk to the VPN provider about it, before you commit.
thanks for your answer.
i have a DNS and my provider does not use CGNAT.
i have no problem with IPV4.
plex does not provide any recommendations ?
Try reading this guide:
https://support.plex.tv/articles/200289506-remote-access/
thank you.
I read and reread it, but it is very generic and apparently oriented towards IPV4 only. moreover, the Plex interface mentions the access path using IPV4.
Apart from the link I provided in my first post, I can’t find anything else.
I will try to find information on the Synology side.
Thanks again for your help.
So does IPv4 remote access work for you and it’s only IPv6 remote access that you can’t get working, or do both not work?
I answer your question conditionally …
Remote access works, but the management interface tells me that remote access does not work.
I am not sure, but I think it is due to IPv6 routing which could cause a fallback to IPv4
The Plex API only uses IPv4 to check the status of remote access, not IPv6. The checks originate from servers with the IP addresses published to the following location by Plex.
https://s3-eu-west-1.amazonaws.com/plex-sidekiq-servers-list/sidekiqIPs.txt
If remote access works for you then it doesn’t really matter what the status shows in the management interface.
While Plex allows you to connect via IPv6 when the option is enabled in network settings, it primarily uses IPv4. It doesn’t publish any IPv6 information back to the plex.tv API which is used by clients to find your server.
It should be doing so if:
- IPv6 support is enabled in PMS’ network settings; and
- Remote access is enabled.
Or: - IPv6 support is enabled in PMS’ network settings; and
- A custom server access URL with an IPv6 address is entered in PMS’ network settings.
This URL can be used to see what is being published to Plex’s servers:
https://plex.tv/api/resources?includeIPv6=1&includeHttps=1&X-Plex-Token=<your_plex_token>
You can find your Plex token using the information in this support article.
I tested this earlier today along with remote access via IPv6. It worked fine with clients which support IPv6. However…
As far as I know, only certain clients can connect via IPv6 (the ones I have specifically tested as working are those for Apple devices, iPhone, iPad, etc…).
You still have to have firewall rules configured on your router to allow IPv6 traffic destined to your Plex server to pass. There’s no NAT for obvious reasons, so routers/firewalls have to be specifically told what traffic to allow to pass. For IPv4 this (normally) happens automatically when the port forward is set up.
This is normal if the only remote connectivity to your system is via IPv6 (or Plex Relay). If your client is connecting via relay, you’ll be limited to 2Mbps and the connection will be shown as “Indirect” in the web UI’s dashboard (Settings → [Server Name] → Dashboard, then click the icon in the top-right to expand the details). If the connection type is “Remote” or “Local” then you have a direct connection to your server.
1 Like
Didn’t know about the includeIPv6=1 flag and always assumed the API was just limited to IPv4, that’s handy.
I can see that it’s listing the IPv6 addresses for my PMS. Interestingly it’s not flagging the status of my IPv6 address as local (i.e. coming up as local="0" rather than local="1"). I assume Plex just checks whether the IP addresses are in the RFC1918 or RFC4193 private address ranges, and if they are then changes the status to local.
Does this potentially means that if you have a local client, it will default to IPv4 to collect to the local PMS as the IPv6 is being flagged as remote?
This makes sense, looking at my firewall logs there’s no IPv6 traffic from Plex’s servers polling my PMS, only on IPv4.
1 Like
I would consider that normal as non-local devices can connect to this address, assuming it’s exposed through the firewall.
I think it has implications for the order in which connections are attempted (e.g. local first), but don’t quote me on that.
Luckily my ISP (Spectrum) hasn’t gone CG-NAT in my area (yet). But I test IPv6 every once in a while to ensure I’ve got a viable fallback plan should they ever decide to.
1 Like
Thank you for all this information.
I was completely unaware of most of these settings.
Specific PMS port is opened in both IPv6 firewall.
I have disabled IPv6 as well as Relay on my two servers.
But this does not change the remote access messages.
Where can I find the server address I’ve mentioned ? I’m not sure I’ve used the reverse URL I’ve configured on my NAS (https://plex..myds.me: => http://localhost:32400)
Please note that PMS supports ipv6, but the clients might not. I don’t know which ones actually do. If searching the forums for answers i would suggest trying for specific clients.
1 Like
The Apple clients (iOS/iPadOS/tvOS) definitely support IPv6, I’m using that right now.
It’s still really annoying that after more than 12 years of foot-dragging, Plex still refuses to make IPv6 connectivity more informative. Just show in Settings - Remote Access which IPv6 is getting advertised (just like with IPv4), that already makes it so much easier for users to get the right info to open their firewall to that IP address. Also, show a message: “you are not reachable over IPv6, please open TCP port 32400 in your firewall”. This forum, Reddit, and tons of other places are now flooded with frustrated posts of people who are behind CG-NAT.
2 Likes
I can confirm that an IPv6-only server is viable if you use Apple devices.
What did the trick for me was this post.
As @certuna mentioned, I’m also quite annoyed by the fact that Plex doesn’t put any effort in making IPv6-only server much easier to setup but most importantly, ensuring that ALL Plex clients support IPv6. Android clients for example doesn’t seem to support it.
In a world where CGNAT is becoming super common, this is quite frustrating to see.
2 Likes
Plex needs to prioritize IPv6 support for all clients not just Apple. That is their problem as almost all new devices have ipv6 support. Also the USA is also getting isps that only give public IPv6 as they themselves don’t have vary many ipv4 addresses and won’t even sell you one.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
