You are more or less correct. One thing to remember, if you want to try this and want secure connections to work you need also an SSL Certificate to match your custom domain (I use Let’s Encrypt, free).
Hi @charlie2alpha, by more or less correct, do you mean that plex.tv will choose between IPv4 and IPv6 according to the user network? Or will it always default to IPv4?
https is running fine, I’ve set up a wildcard certificate that also covers my Plex subdomain. Direct access to my server’s web interface works fine over IPv6 and IPv4. Ping and ping6 gives returns different IPs for the same domain. I can still reach my server’s custom access URL / web interface) even if I fully disable IPv4 support.
I’m just wondering about plex.tv itself. Will it fulfill the request to PMS using IPv4, IPv6 or the client’s default protocol version?
plex.tv will try to use all server access URLs until one of them connects. If it connects via IPv4 or IPv6 that’s up to the operating system and the browser used. I helped a friend recently to setup a custom server access URL because he only had IPv6 (IPv4 only via DS-Lite tunnel). In all cases, the clients connect via IPv6 provided the device used has an IPv6 address.
1 Like
We don’t need custom access URLs for IPv4 so why is this workaround still needed for ‘vanilla’ IPv6 connectivity? Is it really that difficult to implement that this functionality has been pushed forward for at least six years now?
3 Likes
+1
have no more access
Dear all,
I have similar issues. I am a Unitymedia customer with DS-Lite connection. From IPv4 clients I can access plex via a forwarding from feste-ip.net which translates from IPv4 to IPv6. For my home user account this works, tough it keeps reporting: " Not available outside your network
Your server is signed in to Plex, but is not reachable from outside your network."
I entered unter settings -> network “Custom server access URLs” the URL which points to the plex server to propagate its hostname. Somewhat it still does not work.
Is this issues resolved for people with DS-Lite internet connections?
Quite frustrating issue…
Cheers,
Charles
What does your custom server access URL look like?
As far as i know this “not available from the outside” is unreliable, in many cases this is displayed when the server is accessible.
The ‘Custom server access URL’ is http://XXX.feste-ip.net:32400
If I access the given URL from a browser it it reachable.
I’m slightly confused here, you mention earlier that remote access does work:
So which combinations work for you and which don’t?
Indeed, maybe I confuse problems here myself.
I am able to access via feste-ip.net. Also access works through mobile when not connected the local wifi. Should be all ok like this, but the quality is limited to max 320p, also Plex gave a warning that related to connection and quality issues which I cannot totally recall right now.
Major question is how to improve the quality? Maybe I assumed wrongly it is because of an accessibility issue.
Just could get the warning again:
You are not connected directly to XXX.feste-ip.com so streaming quality may be limited. You may be able to connect directly to this server by changing your home network settings.
1 Like
It looks like the connection is indirect (Plex Relay) yes, that means your clients can’t reach the server:
- either the incoming IPv4 ports are closed on the side of feste-ip (unlikely I think, but there might be a setting somewhere?)
- or your ISP runs its own IPv6 firewall blocking all incoming traffic (some do that, Bouygues in France for example)
- or the IPv6 ports are not open on your home router
Thanks for the answer certuna!
Anyhow I’m still quite puzzled because from outside my home network (smartphone, work) when I try to access XXX.feste-ip.net: 32400 the Plex server answers. So, by this I assume the connection from outside is actually working. My home router is not blocking connection via port 32400, or does Plex require other ports as well? I saw some other ports, but they don’t seem essential for access.
Still confused…
So is that a direct connection or indirect?
I suppose that is direct as I type the address into a browser and not using the plex app or the plex.tv website. I also see the names of the libraries but it says “No soup for you! You do not have access to this server”
Any clues?
No I mean, if you go to the server settings in the web view, is there a yellow circle with “!” next to the server name on the left, with “indirect” under it?
Yes, there is the “!” with “indirect” next to the server name if I use an outside connection.
Ok then you’re connecting through Plex Relay, ie both server and clients connect outbound to the Plex relay server, which then sets up a secure IPv4 tunnel. This is the fallback when direct inbound connections to your server do not work.
For IPv4 that’s to be expected (DS-Lite has carrier grade NAT) but your server should in principle be directly accessible over IPv6. Hard to say where it’s going wrong, somewhere between feste-ip, your ISP, your home router or your server.
I was rechecking stuff without finding something. Then I just remembered (because it was so normal to me) that I run Plex in a docker container which complicates things even more. I suspect something there not to be configured properly, but Docker and IPv6 don’t seem to be friends either. Still checking documentation…
6 YEARS, in words: SIX YEARS, and still NOTHING. Pathetic!
2 Likes
