IPV6 and Certificates

Plex Media Server Remote Access
, ,
1

Server Version#: Version 4.69.1
Player Version#: WEB PLAYER
Keeping this simple.

I have a signed certificate for plex.fultonit.net

I have the certificate working perfect on ipv4, I have cloudflare A record plex.fultonit.net pointing to my public with port forward 32400 to internal plex server.

IPV6 i have forward allowed to it’s public on IPV6 over port 32400. in cloudflare I have plex.fultonit.net AAAA record pointing to the plex’s public IPV6 address.

IPV4 through webplayer and dns works fine.
IPV6 through webplayer and dns does not work. it sends me to try and authenticate and immediately tells me i cannot and that’s basically the end of it.

2

We were unable to complete this request.

You will be redirected automatically.

is the error and then I’m redirected to plex.tv

3

you can try enabling Pseudo IPv4 in cloudflare. Not sure if plex will care, but worth a shot. cloudflare->network, halfway down

4

Is TCP port 32400 opened in your router’s IPv6 firewall towards the server?

5

If i disable IPV4 completely IPV6 works.

I think this is more of a feature request now to let you select if plex should prefer IPV6 over IPV4.

By default windows prefers IPV6 on web browser, so I do not know why plex is preferring IPV4 over IPV6

6

Assume that there’s not yet 100% faith in the robustness of their IPv6 implementation, there seem a few loose ends (such as, you can’t set a mix of v4 and v6 subnets in the ‘networks to be treated as local’ settings, etc).

7

Plex ipv6 support is terrible and shameful. IPv6 remote access works only with Apple devices.

8

If I’m not mistaken, it can work with other platforms, if you put a reverse proxy in between (you can run it on the same machine as the Plex server), so:

  1. Remote device connects over IPv6 to reverse proxy (so custom server URL = https://plex.yourdomain.com:443)
  2. Reverse proxy terminates the https connection securely and connects over IPv4 to Plex (plex.yourdomain.com → localhost:32400 or 127.0.0.1:32400)

And yes, it’s shameful when in 2022, networked applications don’t do IPv6 out of the box. Plex is the last application in my home that needs IPv4. But what can we do, we wait until it’s done.

9

Unfortunately my roku’s only do ipv4, so I’m stuck dual stack for the forseeable future.

10

I changed internet providers to T-Mobile home internet. They are Wan IPv6 only. Plex remote access stopped working. Plex Amp is dead. havent found solution for plex Server on windows 10 to use Ipv6 address. still trying to find a hack that will help.

11

T-Mobile blocks all incoming traffic (IPv4 and IPv6), you can’t host anything behind those things. Time for a VPS…

12

Thank You for that information.
I’ve been pulling my hair out trying to get plex and a DC++ peer to peer client to work. They are working in a crippled capacity, and now I know why.
I assume there are ways, like a vpn, but difficult and involves cost.

13

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.