Can't connect remotely via Android

[Morphium 5]

Hi all,

I have Emby running on a Synology - old version 4.7.14.0 because I cannot currently update the Synology (because of Videostation) and that's the latest version, that DSM 7.1 offers. It's running fine in the web app. It also worked fine in the android app for a few days and then suddenly stopped working remotely.

It says: "Unable to Reach Server"

Locally, I still can login. And curiously, my girlfriend can still login remotely as well, as can I in the browser. Not just through Android.

Ports 8096 and 8920 are forwarded to the Synology.

I thought it might be a problem of my phone or my internet provider. However, on a different phone it didn't work for me as well and my girlfriend has the same internet provider. She also has the same app version on Android.

I'm out of ideas. Can somebody help?

 

Edited June 3, 2025 by Morphium

[GrimReaper 4739]

7 minutes ago, Morphium said:

Locally, I still can login. And curiously, my girlfriend can still login remotely as well, as can I in the browser. Not just through Android.

How are you connecting: via remote IP, domain name or Emby Connect? 

[Morphium 5]

I log in via Emby Connect, then add a server via Synology domain (DDNS hostname). And I just saw that this address does not work locally on android and that the remote IP does not work in browser. In Browser (remotely) I'm still logged in with the DDNS hostname. However, my girlfriend did log in with the Synology domain.

Sorry if that's confusing. I only half know what I'm doing here and probably use some words wrong.

[GrimReaper 4739]

I have to admit it is somewhat ambiguous, so let's try to take it step by step in order to get some clarification. 

As per your previous info, you have no issues connecting locally, so let's focus on remote connections. 

As a first step, from your mobile browser (with your cell phone being on mobile data), is your server reachable by entering IP:port in the address bar? 

[Morphium 5]

4 minutes ago, GrimReaper said:

As a first step, from your mobile browser (with your cell phone being on mobile data), is your server reachable by entering IP:port in the address bar?

No

[GrimReaper 4739]

OK, then that's the first thing that needs to be sorted. Could you share a screenshot from the Web app of your server Settings>Network tab, to get an idea of the setup you're running (http/https, reverse proxy, domain etc.)? 

[Morphium 5]

You mean this one? It's the network tab of the synology control panel (sorry, it's in german)

[GrimReaper 4739]

Nope, Emby Server settings, when you access it locally from a browser. 

[Morphium 5]

 

This? Sorry, I'm really a noob

[GrimReaper 4739]

No worries. Yep, that's the one. Also remaining part of those settings. 

[Morphium 5]

 

[GrimReaper 4739]

Thanks. I'd assume you haven't changed anything there as all of those appear as default. Can you confirm in your router that port 8096 is forwarded to LAN adress shown in your Emby Server Dashboard? 

[Morphium 5]

Yes, I would think it's all on default.

I did the port forwarding in the router (tried it also in Synology via UPnP, but neither worked). You see in the router Emby and FTP. FTP is working (through DDNS as well). Without these entries FTP didn't work. So they have to do something. Here's a screenshot from the router:

[Morphium 5]

[GrimReaper 4739]

With my limited understanding of German, that appears in order, external 8096 port forwarded to correct LAN address (though not clear to which internal port it is forwarded to, assuming it is the same port?). Does your Dashboard list remote address as IPv4 or IPv6 and also port 8096? When you tried to connect from your mobile phone, did you type http:// as well, i.e. http://IP:8096, or removed "s" from https://IP:8096 if your mobile browser upgraded address automatically? 

Edited June 3, 2025 by GrimReaper

[Morphium 5]

yes, the are forwarded to the same port. 

My Dashboard shows this (to my understanding it is the remote IPV4 address?). 

I just tried all variations with the address, without anything, with http and with https. As far as I understand, https is not possible with my synology (maybe because of old version, maybe because of missing certificate (which I'm unable to update). When I first set up emby it told me that https does not work and I should try http (I can't really remember, but I probably set it up with DDNS address, so xxxx.synology.me over the http:/app.emby.media link.

[GrimReaper 4739]

Do you have any browser installed on your Synology? If yes, what does canyouseeme.org show for 8096 on your visit from it? 

[Morphium 5]

As far as I know, there is no browser for the synology (maybe some workaround for people that understand it, but certainly not for me).

When I do it in browser with the remote IPV4 address I get this:

That's not good, right?

[Morphium 5]

However, the same goes for Port 21 and that clearly works, as FTP is working with the DDNS hostname (but also not with the IP). In the DDNS settings in synology this is the IP that is listed though.

[Morphium 5]

Can it have something to do with the Internet provider? Because it says that it uses a DS-Lite-Tunnel

And I read somewhere, that this is not a real public IP address? But I don't really understand it.

[GrimReaper 4739]

7 minutes ago, Morphium said:

there is no browser for the synology (maybe some workaround for people that understand it, but certainly not for me).

No native app, but you can install it via docker. 

7 minutes ago, Morphium said:

That's not good, right?

Yeah, if that's the same remote IP, meaning no service is reachable (as in not listening) on port 8096. 

4 minutes ago, Morphium said:

However, the same goes for Port 21 and that clearly works, as FTP is working with the DDNS hostname (but also not with the IP). In the DDNS settings in synology this is the IP that is listed though.

Guess would be Synology is doing some internal re-routing, which would indicate that your server is maybe only reachable by xxx.syno domain name? Can you connect to it from your browser via your domain? 

[GrimReaper 4739]

2 minutes ago, Morphium said:

Can it have something to do with the Internet provider? Because it says that it uses a DS-Lite-Tunnel

And I read somewhere, that this is not a real public IP address? But I don't really understand it.

Does your ISP use CG-NAT? 

[GrimReaper 4739]

15 minutes ago, Morphium said:

DS-Lite-Tunnel

Quote

DS-Lite is used by internet providers that do not have sufficient public IPv4 addresses for their customers and therefore set up IPv6 internet connections with DS-Lite for them. 

With DS-Lite, almost all IPv4 applications can be used without restriction. It is only not possible to access the FRITZ!Box or devices in the home network over the internet via IPv4 because the FRITZ!Box does not obtain a public IPv4 address from the internet service provider. This means that if you are operating servers in the home network, they cannot be accessed from the internet via IPv4.

Guess it does. 

Edited June 3, 2025 by GrimReaper

[Morphium 5]

1 minute ago, GrimReaper said:

Does your ISP use CG-NAT? 

Probably, yes. At least I found a lot of google entries about CG-Nat and my provider. It seems possible though to change it when I change the tarif. Which I woould be willing to do if it's a solution.

4 minutes ago, GrimReaper said:

Can you connect to it from your browser via your domain? 

If you mean whether I can access the synology by typing xxx.synology.me in the browser - no. Neither with https nor with http

[GrimReaper 4739]

1 minute ago, Morphium said:

Probably, yes. At least I found a lot of google entries about CG-Nat and my provider. It seems possible though to change it when I change the tarif. Which I woould be willing to do if it's a solution.

In that case, obtaining static IP (usually costs few bucks) would be the easiest solution; if you're unwilling to take that route, you'd need a way to punch through that with some VPN tunnel or alternative solutions, like TailScale or ZeroTier.