[Solved] Android App not connecting outside

[Gilles990]

Here we go :

<?xml version="1.0" encoding="utf-8"?>
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <BaseUrl />
  <EnableHttps>false</EnableHttps>
  <RequireHttps>false</RequireHttps>
  <InternalHttpPort>8096</InternalHttpPort>
  <InternalHttpsPort>8920</InternalHttpsPort>
  <PublicHttpPort>8096</PublicHttpPort>
  <PublicHttpsPort>8920</PublicHttpsPort>
  <AutoDiscovery>true</AutoDiscovery>
  <EnableUPnP>false</EnableUPnP>
  <EnableIPv4>true</EnableIPv4>
  <EnableIPv6>false</EnableIPv6>
  <EnableRemoteAccess>true</EnableRemoteAccess>
  <LocalNetworkSubnets />
  <LocalNetworkAddresses />
  <KnownProxies>
    <string>Intranet ip server</string>
    <string>Intranet ip Router</string>
  </KnownProxies>
  <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
  <VirtualInterfaceNames>
    <string>veth</string>
  </VirtualInterfaceNames>
  <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
  <PublishedServerUriBySubnet />
  <RemoteIPFilter />
  <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
</NetworkConfiguration>


To find network.xml, on synology it is in /vol1/@appdata/jellyfin/config

[TheDreadPirate]

If you're still on 10.9.7, can you try upgrading to 10.9.11?

[Gilles990]

Same thing with docket 10.9.11.

Very strange so

Browser OK
App Android KO

[Gilles990]

IP V6 was the problem.

Android applications do not switch to ipv4 when ip v6 not available.

I didn't open the route on my router in IP V6.

If my syno use IPV6 .... applications dont work, browsers ok
if my syno doesn't use IP V6, applications work. browsers ok

If ipV6 route is ok on your router everything ok.

It's always workin with browsers.

[DominikFickenwirth]

If my syno use IPV6 .... applications dont work, browsers ok
if my syno doesn't use IP V6, applications work. browsers ok

Could you please specify, what you mean by "Syno uses IPV6" and "Syno doesn't use IPV6"? I'm having the exact same symptoms as you described.

[TheDreadPirate]

If my syno use IPV6 .... applications dont work, browsers ok
if my syno doesn't use IP V6, applications work. browsers ok

Could you please specify, what you mean by "Syno uses IPV6" and "Syno doesn't use IPV6"? I'm having the exact same symptoms as you described.

Some router's don't implement IPv6 very well.  Or don't implement it in a way that would allow the clients to be remotely accessible.

The OP was probably in that situation and they disabled IPv6 on their Synology NAS so that they were IPv4 only.  The server would no longer attempt to make IPv6 connections.

[DominikFickenwirth]

Thank you for your quick reply!

I did not configure DynDNS on my Synology NAS, but on my router. When I check with this tool:
   

I can see that the A-Record (IPv4) and AAAA-Record (IPv6) both point to my router. I can also see that IPv6 connection fails.

Somehow I assumed that the IPv4 port forwarding from my router to my Synology NAS would also work for connections coming in via the public IPv6 address of my router. This is not the case: I don't have IPv6 configured on my network, so my Synology NAS does not have an IPv6 address. Therefore, the router would have to forward the incoming IPv6 request to the IPv4 address of the NAS (which it doesn't do).

As you suspected, my router does indeed block all incoming IPv6 requests. Also, in the settings of my router, it's not possible to force DynDNS to send only the IPv4 address.

I have now configured DynDNS directly in my Synology NAS instead of the router, sending only an IPv4 address. The Android app works without any problems!