Search the Community

cant connect over remote unless on the internal via tailscale or something like that. realistically want it linked to my domain and be able to remote connect safely without other clients needing anything but emby. i have port forwarded all relevant ports to the correct internal ips. tried mullvad and proton for vpns but they dont offer a dedicated open port for me to use. using canyouseeme to check if ports are open shows nothing but either refused or time outs on the ping. thanks for reading

I am running an Emby Server on windows 11, have a premiere account and until now everything is running fine. I am looking to move ISP, but the new provider only offers CGNAT for IPv4, it also offers IPv6. Static IPv4 is not a realistic option - large price jump and I would loose all IPv6. My DDNS service supports IPv4 and IPv6. Once CGNAT is switched on, I know I will loose port forwarding on the IPv4 address, but want to know if Emby still work with traffic coming via IPv6 or if I need to consider other solutions. The LAN supports IPv4 and IPv6 and the router port forwarding rules are to IPv4 LAN addresses (ASUS RT-AX88U) Thanks Archiel

As more and more ISP's are implementing the dreaded CGNAT due to IPv4 availability, there are more and more support requests in the forums on why their emby 'remote access' is not working. Would it be an idea to test for CGNAT when the 'Remote Access' button is selected in emby ? It's a simple test and then the user can simply be warned that emby will not be able to provide a remote access service on this ISP connection. Maybe provide a link to a 3rd party tunnel solution, but advising this is not supported by emby blah blah. For those that are unaware what CGNAT is (Carrier Grade Network Address Translation) - this is the ISP's own 'private' network in front of the 'Public' internet. It effectively 'shares' public IP addresses with all the IP's on their private network. Subsequently you cannot use it for 'incoming' connections - because that public IP is not exclusive or available to you, it's shared with many others behind a 'private' IP address. There are solutions around it - but they involve a network 'tunnel' - and will be beyond a lot of the users networking knowledge and capabilities.