Apple TV App cannot connect via DDNS on port 8096, while iOS app and browsers work

[famarch 0]

Hello,

I am seeing a reproducible issue with the Apple TV app and would like to clarify whether this is a known problem or a bug.

My Emby server is reachable externally via DDNS on port 8096.

What works:
- access via Safari and other web browsers using the DDNS address
- access via the iPhone/iOS Emby app using the same DDNS address

What does not work:
- access via the Apple TV Emby app using the same DDNS address

So the basic pattern is:
DDNS + port 8096 works in browser and iOS app, but not in the Apple TV app.

My question is:
Is there a known issue with the Apple TV app regarding external connections via DDNS and port 8096, especially compared to Safari and the iOS app?

I would also like to know whether the Apple TV app handles DDNS, IPv4/IPv6, or external HTTP connections differently from the iOS app and browser access.

Thanks.

appleTV: A2169, tvos 26.4

emby app on tvOS latest version

[famarch 0]

Anyone there?

[Luke 42293]

Hi, what exactly happens? How are you initiating the connection?

[cul8rmom1 8]

i have no problems doing this.  My ddns services are provided by my synology account.  I am actually routing thru 2 subnets to get to my machine without issue. 

Yeah so are you adding the connection manually?  Are you disabling your wifi on your cell devices when you test?

what is the dns server on your devices?

(apple can do some weird stuff with their secure dns and icloud relay on non appletv devices.)

does it work with the ipaddress and not the name?(if it doesnt work with the resolved ip you have other issues.)

 

 

[famarch 0]

Thank you for your response. I’ll describe the problem in more detail over the weekend.

[Luke 42293]

18 minutes ago, famarch said:

 

Thank you for your response. I’ll describe the problem in more detail over the weekend.

HI, that would be great. Thanks !

[famarch 0]

Hello,

thank you for your replies. Here are some more precise details about the issue.

Setup:

- Emby Server 4.9.3.0

- Synology DS1819+

- DSM 6.2.4-25556 Update 8

- Apple TV A2169 with tvOS 26.4

- iPhone 14 Pro with iOS 26.3.1

- MacBook Pro with macOS 26.3.1

The Emby server is located at a different site and therefore in a different LAN than the Apple TV, iPhone and MacBook Pro. So these are external/remote access tests.

 

How I initiate the connection on Apple TV:

I add the server manually in the Apple TV Emby app via “Connect to Server”. I manually enter the hostname and port. After pressing Connect, the app shows that the server cannot be reached. Screenshots are attached.

 

What works:

- MacBook Pro: Safari and Firefox can reach the server externally

- iPhone 14 Pro: Safari can reach the server externally

- iPhone 14 Pro: Emby iOS app can also reach the same server externally

What does not work:

- Apple TV: Emby app cannot connect to the same server when entered manually

 

Tested connection methods:

1. http://xxxxx.synology.me:8096

- works on MacBook Pro in Safari / Firefox

- works on iPhone in Safari

- works on iPhone in the Emby app

- does not work in the Apple TV Emby app

 

2. http://xx.xx.xx.xx:8096

- works on MacBook Pro in Safari / Firefox

- works on iPhone in Safari

- works on iPhone in the Emby app

- does not work in the Apple TV Emby app

 

3. https://xxxxx.synology.me:8920

- tested after installing a valid certificate

- works on MacBook Pro in Safari / Firefox

- works on iPhone in Safari

- works on iPhone in the Emby app

- does not work in the Apple TV Emby app

 

4. https://xx.xx.xx.xx:8920

- also tested for completeness

- in Safari, this shows the expected certificate warning because the certificate matches the hostname, not the raw IP

- after manually accepting the warning, the connection still works in Safari

- in the iOS and appleTV app, this fails with “Unable to reach server"

- which is expected, since app-based clients typically do not offer the same certificate warning override/handling that a browser does

 

Additional note regarding network tests:

I tested both

- through normal Wi-Fi via router/modem

- and through iPhone hotspot

So this was not just one single network path.

 

About DNS:

I can check the exact DNS server settings on the devices if needed. However, DNS resolution itself does not seem to be the main issue anymore, because:

- the DDNS hostname works on MacBook Pro and iPhone

- the Emby iOS app also works with the same DDNS hostname

- and even direct IP tests on Apple TV also fail

 

Thanks in advance for any ideas.