Quickconnect works the same way as Plex relay so the connection is indirect and with limited bandwidth.
Turn off Plex relay, setup ipv6 ddns and fill with it custom url, open port 32400 in ipv6 firewall and you should be good. Keep in mind that all clients must have ipv6 connectivity to be able access PMS remotely and directly.
Some people say that ipv6 remote access works only with apple devices and Plex ipv6 implementation sucks. So keep it in mind.
I don’t know what quick connect is but all Plex clients try all connection options until they find a direct connection before falling back to relay.
You can set up DDNS but that won’t work with TLS as the cert will be invalid.
Don’t pay attention to whatever is on the “remote access” config page of your Plex server, that page has no bearing on the IPv6 connection (although some say it needs to be enabled there even if it shows as not working - I haven’t tested that).
Direct connection will only work if you can connect to the plex server directly (like with the direct URL) from the network where the client is.
I have successfully done it from Apple TVs, other Apple devices, Android TVs, Plex desktop apps, PlayStations and FireTVs. They all seem to work just fine as long as the network where the client is has direct access to the server. If that’s not in place, that’s what you need to fix.
I will try that this week and I come back, thanks for the informations.
Yeah, don’t be fooled by the red “remote access” test in the settings, this test only works over IPv4: it tests by connecting to the domain plex.tv, which has no AAAA record (!) so will never work over IPv6.
We’re now in an annoying transition phase where about half the world’s home connections have their IPv4 behind CG-NAT and can only run servers over IPv6, but the other half of the world has no IPv6 yet, so cannot connect to those servers.
Plex should really consider running a reverse proxy service for their Pass holders to solve this issue of IPv4 clients connecting to IPv6 servers, instead of Plex Relay. Can’t be terribly hard technically - they already have all the pieces of the puzzle (DDNS, relay server bandwidth) - and as IPv4-only endpoints get less and less common (but likely never quite zero), it’s a service with diminishing bandwidth requirements going forward.
I don’t see how a reverse proxy would provide any benefit over the current relay implementation. They would be doing the same thing, the only difference would be the direction of the connections between the relay/proxy and the Plex server.
Bandwidth and security requirements should be equivalent on either solution.
Plex should have provided proper ipv6 support years ago.
No arguments here. The current implementation (or lack thereof) is unacceptable in 2022, especially given how prevalent CGNAT is these days.
A reverse proxy would be different - the Plex proxy would be connecting to PMS on-demand (like a client with direct connections), while with Relay PMS has to keep an outgoing tunnel to Plex alive permanently.
Plex’s reluctance in implementing IPv6 is annoying - if you see the timeline in this topic, the need was flagged back in 2013 when the first large-scale rollout of DS-Lite started for residential connections in Germany, but was more or less ignored until recently. As of today, Plex works partly over IPv6, but only in dual stack environments - Plex can not run in a single stack environment. Also, there are some rough edges like the inability to whitelist a mixed list of IPv4 and IPv6 subnets, and the “remotely accessible” test only checks IPv4 connectivity.
While dual stack is and will probably remain the norm for residential connections for a while, VPS hosting providers are increasingly moving to the single stack + NAT64 model (with IPv4 as a paid add-on), so for those Plex users with paid hosting this is going to be an annoying limitation.
Every other Plex release, I am hopeful and turn on Remote Access and typically get Fully accessible outside your network in the Settings dialogue. However, when I try to access my plex server from anywhere else, I get a No Internet Connection error. Remote access never worked for me - for almost 10 years now.
As this closed request mentioned, I do suspect the issue is with DS-Lite.
In the hope that IPv6 eventually gets “fixed” and allows remote access to my Plex server, I wanted to give this thread a bump up.
Remote access works with IPv6 just fine but how can you be fully accessible outside your network with legacy IP only? What a misleading statement.
A service that relies on remote access should promote IPv6 with excellent implementation.
Hi @premikkoci - I assume your comment was meant for me and I apologize if my post was not clear.
The parts I typed in italics were what the application displayed - not what was actually the case.
To clarify:
So despite the server settings temporarily suggesting, that there was some remote connection possible, I have never seen this work in practice.
I also know that I do not get a fully qualified IP4 connection from my provider, but a DS-Lite connection. If this is the root cause of my issues, I cannot really say, but DS-Lite seems to be a common theme among people who have issues with their remote connection.
That remote access page checks only legacy IP connectivity.
@premikkoci, I am not sure what you mean by “legacy IP connectivity”. Do you refer to IPv4? If so, how could one check IPv6 remote connectivity?
Anyone tried this, super simple but seemed to work for me.
"I found a workaround that doesn’t require a custom domain or SSL cert. Not sure if it was somewhere in the thread I just found it by guessing URL’s.
Under Custom server access URLs enter the IPv6 address in the format below:
https://xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx.serverid.plex.direct:32400
Note all parts must be entered (cannot use :: abbreviation)."
Yep, that’s how most of us have it working. You’ll find plenty of references to this solution on this thread if you don’t mind scrolling back the 11 years this issue has been open. sigh
Just wanted to hop into this thread to up the count of someone needing this. It’s been 11 years, and I would like the capability of having better than a 2MB connection. The Custom Server Access URL worked for me and then I updated the app and haven’t been able to get it working since. Could we either get this capability or a higher relay speed?
UPDATE: For those with a similar issue. I forgot that I had reissued the Let’s encrypt which gave me a new IP and forgot to setup the new IP in the Custom URL. It’s working now.
I’ve noticed that many people—including myself—have managed to get Plex working over IPv6 with little to no assistance from Plex itself, resorting instead to workarounds like VPNs, VPSs, Cloudflare, and other third‑party tools. Since full IPv6 support could be implemented quite easily on the Plex side, it’s a shame that years have passed without any clear progress.
I’m able to use IPv6-only on almost all web browsers, without any additional software or setup, but can’t connect to it through any apps, iOS or Android. Plex employers should give this a more important note, especially because IPv6 adoption is only going to increase worldwide overtime.
100% agree
Still no news from the Plex team on this. So sad honestly.
They keep adding things that improve plex But don’t fix a basic networking issue…….
