Can't connect remotely via Android

[Morphium 5]

2 minutes ago, GrimReaper said:

In that case, obtaining static IP (usually costs few bucks) would be the easiest solution

Through my provider, right? 

I'm totally willing to do that. But still wondering, why it works through the remote browser and my girlfriends phone (and my own phone at the beginning) with the DDNS address. I was even able to login last night for a short moment but then it stopped again.

I just tried to put the DDNS address under external domain in the network settings. But that didn't work either.

[GrimReaper 4739]

Just now, Morphium said:

Through my provider, right?

Right. 

1 minute ago, Morphium said:

But still wondering, why it works through the remote browser

Not sure I got that one, works how? You tested with remote IP and with domain name from mobile browser - neither worked, so what do you mean by "remote browser"? 

[GrimReaper 4739]

15 minutes ago, Morphium said:

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

Did you add port here, i.e. xxx.synology.me:8096? 

[Morphium 5]

1 minute ago, GrimReaper said:

so what do you mean by "remote browser"? 

I have remote-access to my desktop at home, where I am logged in through the DDNS address:

curiously that doesn't work on the phone with mobile internet.

[Morphium 5]

3 minutes ago, GrimReaper said:

Did you add port here, i.e. xxx.synology.me:8096? 

Did that now and neither https nor http work (did it via the browser on my remote-computer)

[GrimReaper 4739]

2 minutes ago, Morphium said:

Did that now and neither https nor http work (did it via the browser on my remote-computer)

Maybe your router doesn't support hairpinning - if you do it from remote location (like wherever you are now), does the same occur? 

Edited June 3, 2025 by GrimReaper

[Morphium 5]

At the moment I am at the location of the synology. So if I understand it right, I cannot use the remote IPV4 address here (and it doesn't wok). When I use the local IP:port it opens the emby web app.

[GrimReaper 4739]

15 minutes ago, Morphium said:

I have remote-access to my desktop at home, where I am logged in through the DDNS address:

curiously that doesn't work on the phone with mobile internet.

 

6 minutes ago, Morphium said:

At the moment I am at the location of the synology.

I'm trying to make some sense of it: if I understood it correctly, your server (your Synology) is on a remote location from your home, hence this:

12 minutes ago, Morphium said:

Did that now and neither https nor http work (did it via the browser on my remote-computer)

was actually remote attempt. 

If that is the case, could you login here:

15 minutes ago, Morphium said:

I have remote-access to my desktop at home, where I am logged in through the DDNS address:

browse to any library and then download server log and attach it to your post here? There's a switch to Anonymize logs (so your external IPs/domain will be masked), confirm it's toggled On before you download it

Edited June 3, 2025 by GrimReaper

[Morphium 5]

Not sure how to download it. It opened the log in the browser and I copy/pasted it into a txt-file.

log.txt

And yes, my Synology is in my office (where I am right now) and I have remote access to my computer at home.

[GrimReaper 4739]

1 hour ago, Morphium said:

Not sure how to download it.

Log Files

1 hour ago, Morphium said:

It opened the log in the browser and I copy/pasted it into a txt-file.

Net-effect is the same, that just took you a bit more time. 

1 hour ago, Morphium said:

 

log.txt 47.1 kB · 1 download

That's really puzzling. Multiple remote connections established can be observed:

Quote

2025-06-03 21:34:45.042 Info Server: http/1.1 POST http://host2:8096/emby/Users/authenticatebyname?X-Emby-Client=Emby+Web&X-Emby-Device-Name=Edge+Windows&X-Emby-Device-Id=0e89da81-e9a7-44bf-a74c-a4f232970849&X-Emby-Client-Version=4.8.11.44&X-Emby-Language=en-us. Accept=application/json, Connection=keep-alive, Host=xxxxxx.synology.me:8096, User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36 Edg/136.0.0.0, Accept-Encoding=gzip, deflate, Accept-Language=de,de-DE;q=0.9,en;q=0.8,en-GB;q=0.7,en-US;q=0.6, Content-Type=application/x-www-form-urlencoded; charset=UTF-8, Origin=http://app.emby.media, Referer=http://app.emby.media/, Content-Length=28
2025-06-03 21:34:45.060 Info UserManager: Authentication request for admin has succeeded.
2025-06-03 21:34:45.063 Info SessionManager: Creating new access token for user 1

Why using same address fails from your browser, I honestly can't say (except maybe your browser not allowing insecure connections). 

As a test, if you try to establish connection manually from your Android app, with http://xxxx.synology.me and port 8096, does it also fail? 

 

Edit: As a sidenote, you might wanna increase your inotify instances limit as default value has been reached. 

 

Edited June 3, 2025 by GrimReaper

[Morphium 5]

18 minutes ago, GrimReaper said:

As a test, if you try to establish connection manually from your Android app, with http://xxxx.synology.me and port 8096, does it also fail? 

Yes, I tried that multiple times.

I looked at the DDNS address by synology again and it sets up IPV4 and IPV6 whereas other providers do only seem to set up IPV4? I understand DDNS correctly as a forwarding to an ever changing IP adress, right? 

So maybe it works on my browser at home because he does not forward to the IPV4 address but to the IPV6 address, which might be static? Why it only works in this browser and not over mobile internet, though, i can't imagine.

So, shall I still change my internet package? I can try that tomorrow.

[tedfroop21 86]

No MAC address filter?  Android likes random MAC addresses and can have different settings for local network and mobile network.  

[GrimReaper 4739]

14 minutes ago, Morphium said:

I understand DDNS correctly as a forwarding to an ever changing IP adress, right? 

Correct, but maybe Synology is doing some additional steps, like creating a tunnel of their own in the process (VPN-esque, with their own devices, and re-routing all traffic). I have no idea, that's just an assumption. Though that should work from anywhere, regardless of the app used, if that were the case. 

14 minutes ago, Morphium said:

So maybe it works on my browser at home because he does not forward to the IPV4 address but to the IPV6 address, which might be static?

Wouldn't think so, as most modern browsers should actually attempt to use IPv6 connection first, if available, and switch to IPv4 if it fails after a very short timeout. 

14 minutes ago, Morphium said:

So, shall I still change my internet package? I can try that tomorrow.

I'd hold on with that for the moment, some other fellow user might have some idea that hasn't been explored yet. 

Edited June 3, 2025 by GrimReaper

[Morphium 5]

21 minutes ago, tedfroop21 said:

No MAC address filter?  Android likes random MAC addresses and can have different settings for local network and mobile network.  

I'm sorry. I don't understand that. Are you talking about the mac address of the phone? I can enter the router as well as the Synology with the phone via WLAN. So there shouldn't be any general connectivity issue, right?

[Morphium 5]

1 hour ago, GrimReaper said:

Edit: As a sidenote, you might wanna increase your inotify instances limit as default value has been reached. 

At least these inotify errors are gone now. Thanks for that. I didn't notice anything not working, but probably still for the best.

On my home computer it's opening regardless of the browser (edge, chrome, firefox).

On my phone it's also opening over local wifi now (managed to make an exception for xxx.synology.me in the router, so I guess he is now able to open a remote PIV4 address), but not on mobile data (neither 5G nor LTE). The chrome browser on my phone does allow insecure connections.

[GrimReaper 4739]

10 minutes ago, Morphium said:

On my home computer it's opening regardless of the browser (edge, chrome, firefox).

 

10 minutes ago, Morphium said:

but not on mobile data (neither 5G nor LTE). The chrome browser on my phone does allow insecure connections.

As said, I have no explanation for that. And honestly would've thought it impossible, before this case, considering those are all remote connections. 

@Q-Droid @rbjtech @Neminemanything comes to mind here (yeah, it's a bit long-ish read)? 

Edited June 3, 2025 by GrimReaper

[Morphium 5]

Additional information: I just got home (so I am remote now, as the Synology is in the office)) and it works over W-Lan on the phone. Up until now I probably didn't realize that I was not in W-Lan at home. That's why it worked sometimes and sometimes not. So at my phone it's definitely the mobile connection, that is the problem. BUT: At my girlfriends phone it's working either way. So it can't be the ISP. She has the same provider.

Edited June 3, 2025 by Morphium

[GrimReaper 4739]

13 minutes ago, Morphium said:

BUT: At my girlfriends phone it's working either way.

That's utterly confusing. Can you access it through http://app.emby.media (both through Connect and manual connection) from your phone browser while on LAN? 

[Morphium 5]

5 minutes ago, GrimReaper said:

Can you access it through http://app.emby.media (both through Connect and manual connection) from your phone browser while on LAN?

No I can't. Really strange. It only works through the app

[Q-Droid 989]

I can only wonder if the connections that are working with DNS/DDNS are resolving to an IPv6 address. The ISP shouldn't have limits or restrictions with IPv6 like they do with IPv4.

Edit to add: You should check if this is the case and if you have IPv6 disabled on some devices.

 

Edited June 3, 2025 by Q-Droid

[Morphium 5]

At my girlfriend's phone it also does not work via browser.

[Morphium 5]

1 minute ago, Q-Droid said:

I can only wonder if the connections that are working with DNS/DDNS are resolving to an IPv6 address. The ISP shouldn't have limits or restrictions with IPv6 like they don with IPv4.

 

I can only say that the IPV6 address is listed in the DDNS. So, yeah, if it's a problem with a missing static IPV4 adress, shouldn't it work over the IPV6 address?

[GrimReaper 4739]

Since we're in experimenting territory, does http://[your IPv6 address]:8096 from your mobile browser let you in (notice the square brackets [] before and after IP)? 

[Morphium 5]

14 minutes ago, Q-Droid said:

Edit to add: You should check if this is the case and if you have IPv6 disabled on some devices.

Ok, so the APN of my phone was set to IPV4. Switched it to IPV4+IPV6. Now it's working on mobile connection. On my girlfriend's phone it was set to IPV4/IPV6. So that's the reason it was working there.

Still not working in browser (neither on W-Lan nor mobile). That's not really needed though, of course.

[Morphium 5]

5 minutes ago, GrimReaper said:

Since we're in experimenting territory, does http://[your IPv6 address]:8096 from your mobile browser let you in (notice the square brackets [] before and after IP)? 

Yes! That works!