What settings did you set when opening your firewall please?
@WesMaher I do not use IPV4, I can not use it, the IPV4 is CGNAT. If my iPhone is in a IPV4 environment I only get a connection with the relay server.
Opening the firewall depends on the router you use.
My firewall is configured “deny all”. In the setting I open the ip adress of my PMS for incoming traffic.
Thanks @AViering - so when you opened the router for incoming traffic what settings did you specify, did you have to create a rule which included your IPv6 address or just a general incoming rule to the PMS server?
I use a Lancom 1793VA router. The firewall setting for IPV6 allow forwarding of PMS IPV6 address, I allow http, https and tcp traffic from any host.
you got a PM
The PMS server.
IPv6 doesn’t typically require the same port-forwarding that IPv4+NAT requires.
You will probably need to allow traffic to the Plex IPv6 address in your router’s firewall configuration.
A reasonable IPv6 incoming firewall rule might look like this:
- From any host
- From any source port
- To the PMS server’s IPv6 address
- To the PMS destination port (32400)
No - good observation!
/web is necessary when manually browsing to a Plex server.
It’s not necessary (or appropriate) for client → server discovery using the Custom server access URLs field.
Automatic IPv6 registration appears to be functional in Plex Media Server and the Plex Cloud. This may remove the need to manually craft URLs.
This appears to be all that’s required in PMS:
-
Settings→Network→Enable server support for IPv6 -
Open TCP 32400 in the firewall. IPv6 doesn’t require NAT or Port Forwarding, but does require the port to be open. Plex always listens on 32400.
IPv6 addresses appear to be published whether Remote Access is enabled or not. Remote Access is still useful for IPv4 and Relay.
There doesn’t seem to be any connectivity testing. The addresses are registered with MyPlex whether the ports are open or not.
It appears that Global Unicast and Unique Local IPv6 addresses are registered with MyPlex. Plex appears to treat both as Remote. Link Local addresses aren’t registered. I think the assumption is that IPv4 will be available on the LAN.
I know that iOS and Apple TV work well with IPv6 connections. I haven’t investigated other client types. The iOS Plex App appears to prefer IPv4 if it’s available.
I notice that when IPv6 is enabled, there’s a very strange entry on the Remote Access screen:
That doesn’t make much sense. There’s no IPv4 → IPv6 NAT being performed, and that’s the Link Local IPv6 address, which isn’t registered with MyPlex.
I think this is just a display bug when Enable server support for IPv6 is active. The Private address displayed here should still be the local IPv4 address.
Quick question. Regarding the IPv6 side of things, if the device you are using to access your Plex server remotely doesn’t have an IPv6 address, this won’t work, is that correct?
If a server is configured with only IPv6 then the client must also support IPv6.
(with few exceptions)
The Plex server?
I’m specifically talking about Starlink in this instance. They don’t provide public IPv4 addresses, but do provide IPv6 addresses. I’ve read some info that suggested using the methods mentioned here might help with Plex remote access. But can’t get it working. The devices I am using to test are mobile connections that receive IPv4 address, but not IPv6 addresses. Not sure if that matters or not?
Keep in mind only iOS/tvOS clients are currently able to establish a remote connection over IPv6 (not sure though if they need to also have an IPv6 address themselves… but I don’t think so).
ah ok, so no go for Android phones?
You can install cloudflares app warp 1.1.1.1 to get ipv6 connectivity if your ISP or cellural carrier provide only legacy internet protocol.
That’s helpful if the client app itself supports IPv6. I haven’t tested on Android, but per @tom80H’s comment, I don’t have the impression that the Plex Android app supports IPv6.
I wouldn’t try to run a server on Starlink.
+1
9 years after the first message and 4 years after @ChunckPa said they are working on it, it is the same issue. When your ISP does not provide you IPv4 you cannot have remote access…
1 Like
I can found the ipv6 addr in token list, I can browse it access the web, but the IOS client look like still try use the ipv4 to connect.
In the IOS client, it show the PMS was offline.
Could you give some suggestion?
Not sure what you mean.
At its core, this is about having a proper remote access setup that works through your IPv6 environment. There’s been no separate settings to activate this in the iOS/tvOS apps.
As a side note… I just successfully connected to my PMS through Plex Web while away from home (IPv6-only ISP) → there’s been no need to enter the (complex and changing) IPv6 address – just using https://app.plex.tv/desktop
2 Likes
changed to new Internet provider using shared IPv4 on WAN. real WAN is IPv6.
no more Remote connection to PMS. No PlexAmp.
This tread request for IPv6 support has been going on for 10 years???
tried tunneling apps, nothing but a waste of time. I give up!
I guess when enough people overload there remote relay access they might pay some attention to the problem…Crickets
@Woogetybop This thread is obviously immense and quite old, so you might have missed it but there’s a workaround. It’s certainly not as simple as things should be but it works.
First thing is to find your direct URL:
Then add it in Server settings → Network → Custom server access URLs.
Also please click Vote at the top of this thread so Plex actually do something about this issue. Eventually.
