Is it possible that in a version of emby a "ping pong" is performed in websocket to maintain a connection via a reverse proxy? There are solutions around it - but they involve a network 'tunnel' - and will be beyond a lot of the users networking knowledge and capabilities. 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. It effectively 'shares' public IP addresses with all the IP's on their private network. Maybe provide a link to a 3rd party tunnel solution, but advising this is not supported by emby blah blah.įor 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'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. Would it be an idea to test for CGNAT when the 'Remote Access' button is selected in emby ? 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |