Emby Remote Connections on CGNAT Internet Service

[ginjaninja 607]

I am on Gigaclear service that tech support says uses CGNAT and DHCP. They say ive always been on cgnat but im not sure.

I use DDNS to publish a static fqdn.

I have port forwarding for 8920 configured on my router to the emby service

Remote access via emby clients still seems to be working. Some users have reported issues but when we look into it... things are working. my mobile phone emby client always work when i test it on internet only [wifi disabled].

The Alexa skill is now no longer working. I can talk to the skill and it can issue API requests to my server and the skills say that it is playing something but nothing comes out.

Anyways are there any suggestions for using Emby [remote connections/services] when hosted behind CGNAT?

Can Emby work reliably on CGNAT?does Emby/network require something special config wise?

If the Alexa skill is successfully querying my server but no sound comes out...any troubleshooting advice please? is this just an Alexa skill issue perhaps? not sure if i have a generally connectivity issue or an alexa skill issue.

thank you

Windows 11 22H2, Emby 4.10.0.13, Amazon Echo Dots

 

Edited 13 hours ago by ginjaninja

[pwhodges 2065]

CGNAT should be blocking your remote access - I can't explain the quirk that your implementation seems to have if I read your description aright, and I wouldn't expect it to persist.

The only way to get around a properly operating CGNAT is to use some kind of tunnel.  Some people use a VPN, but a common recommendation in recent months has been to use Tailscale (I believe the free tier can be used if you don't require other facilities).

Paul

[ginjaninja 607]

Thanks Paul, i will look into tailscale.

 

do you think the fact that remote access via emby clients is demonstrably working and that my port forwarding is working (if i disable the port forwarding rule everything stops) necessarily shows that i cant be on CGNAT /  CGNAT is not my issue?

edit: the issue may be that Alexa simply does not like the URL/Webservice provided by skill. The skill can query the API and a url can be seen in logs to be given to echo dot to initiate playback, but then nothing.

I see conflicting reports about Alexa skills having to use 443, but have tried with 443 just in case.

I see some evidence that Alexa is happy to use certificates provided by zerossl and the sectigo root ca.

I have no problems using the webservice/api via a browser on the internet..the issue does seem limited to Alexa. Maybe Alexa just doesnt like something about my certificate or that im on a dynamic dns fqdn.

Edited Tuesday at 07:21 PM by ginjaninja

[ginjaninja 607]

Google says cgnat has a specific ip range and that my wan ip is not part of cgnat...so i may have been given a bum steer by my isp. I have opened a ticket on the alexa forum to discuss the alexa issue specifically.

[pwhodges 2065]

Is the WAN address on your router the same as you see when using a website that displays your IP? 

Is the WAN address in any of the private ranges, or does it start with "100." (part of which range is specifically allocated for cgNAT use)? 

Do you have IPv6 enabled - in which case maybe you are using IPv6 on the occasions when the connection works (cgNAT is only applicable to IPv4)?

Paul

[ginjaninja 607]

8 hours ago, pwhodges said:

Is the WAN address on your router the same as you see when using a website that displays your IP? 

Is the WAN address in any of the private ranges, or does it start with "100." (part of which range is specifically allocated for cgNAT use)? 

Do you have IPv6 enabled - in which case maybe you are using IPv6 on the occasions when the connection works (cgNAT is only applicable to IPv4)?

Paul

Thanks @pwhodges, yes my wan address and "what is my ip" give the same IP and it is NOT in 100. range.

My router does not have an IPv6 address and my dns has no aaaa record. ipconfig/all on my windows server gives no ipv6 address. so my best guess is i am solidly on ipv4.

If im not on CGNAT then i think i just went down a wormhole of misguided hypothesis/analysis...maybe i just have an alexa issue.