T-Mobile

[evanover 2]

Moved to t-Mobile fiber which used CGNat, Have got access to Emby server from outside using DDns and tunnel. But the app will not connect using the same FQDN and port it says unable to reach server. 

[visproduction 369]

Tips on finding IP address and other DNS issues with t-mobile.

In general
 https://windowsreport.com/ip-address-not-reachable/

Known issue / limitation with T-Mobile - some addresses are unreachable by design.

 https://www.reddit.com/r/tmobileisp/comments/qp2r5q/certain_websites_do_not_allow_access_through/

 

[evanover 2]

Let me clear this up some. I can get to Emby using a browser by the FQDN. But not by the Emby app using the same FQDN. 

[Luke 42985]

How are you trying to do that? What exactly is happening?

[evanover 2]

Using a no-IP domain name and using the no-ip client with a tunnel set up. Can get to the server outside of local network using a browser. But when trying to use the android emby app it returns server unreachable.

[Luke 42985]

Are you sure you're trying to connect using the correct address?

[evanover 2]

Using the same name and port for both the browser and the app. 

[TMCsw 293]

Try setting the port in the app to 443 or 80 or 8096 or 8920. 

Otherwise, you need to look more closely at how an:

5 hours ago, evanover said:

no-ip client with a tunnel

works...

[evanover 2]

port is set to 8096

[TMCsw 293]

Have you tried the other ports I listed?

[ebr 16668]

9 hours ago, evanover said:

Using the same name and port for both the browser and the app. 

But what about protocol?  Are you sure those are the same?  The browser may be using https while the app http...

[evanover 2]

Both are using HTTP://domain.name,  port 8096