I have two PLEX Servers (Old one is DELL Windows 10 Home and new one is ASUS Windows 10 Pro), both accessing the same media stored on the ASUS. I moved all my external drives on to the ASUS as internal and shared the drives.
No problems with the server on the old DELL Server, but the new server continually has issues with some or all streaming devices (LG WB OS PLEX, Apple TV PLEX app, Roku PLEX app, Fire TV App)
So sometimes it is only on one app other times all. Sometimes the server appears to be working and I am looking on the web browser and it loses connection with the app.
I am at a loss. Been dealing with this or 2 - 3 months
If you are behind a CGNat afaik you need to contact your ISP to try to get a static public IP. Because a CGNAT basically creates a double nat situation where you don’t have access to the public facing router. Unfortunately many ISPs will charge for this.
Really haven’t made much progress here. I did contact my ISP and confirm I am under CGNAT for IPV4 but have a public facing IPV6 address.
I’ve continued to try and resolve this on my own, but am still struggling to get anything connected on my Samsung TV and my Apple devices are still connecting indirectly.
I understand the for IPV6 to work, I either need an AAAA record or use a custom URL within the PLEX server.
I use a DDNS for my router for other reasons which I imagine should work. Can I just add the custom.ddnsserveraddress.com + port number into the custom URL field? I have IPV4 and IPV6 enabled in the router and the server.
Is there a simple way to get this working? It seems that IPV6 has been a tossed around issue for quite some time. I think it can work, the question is how to get it running for easily for everyone, especially those of us who have a PLEX PASS.
CG-NAT is annoying yes, but it’s widespread now and that’s the future.
Getting Plex to be accessible over IPv6 isn’t too difficult (see this), but do realise: the clients who connect from the outside also need to be on IPv6. If your mobile phone carrier or the network at work are still IPv4 only, you still won’t be able to reach your server.
I was traveling so I wasn’t able to respond sooner.
I have checked with my ISP and they have an IPv4 option but I’m not sure I need it. I have a DynDNS that is associated with my router. Can I just add https://mycustom.dns.com:32400 to my configuration in Custom server access URLs?
The problem with CG-NAT is not with DNS. No matter what the DDNS address resolves to, if the NAT server on the ISP’s side doesn’t map the required incoming ports to your private address, remote access won’t be possible.
Don’t get me wrong, I’m not being combative. I’m just trying to get this working. I really like Plex! I’m sure the issue is my expertise.
I’m just trying to get this working remotely. I can get a fixed ipv4 address but I only casually use remote access so I’m looking for an easy solution.
So as you can imagine, things are never as simple as they first appear to be. My setup involves not only Plex, but also a VPN service. The service prefers only ipv4. So I’m moving the clients that require the service to their own dedicated situation and then I’ll be able to test IPv6 with Plex and make sure everything else works.
I will post when I get the testing and reconfiguration completed. Thanks for your advice.