Emby Remote Not Working

[robertcrossuk 0]

Hello, my Emby remote isn't working. I've followed the Connectivity troubleshooting (https://emby.media/support/articles/Connectivity.html) but still can't connect. See below for status. Red masks are my emby server/home static IP from my ISP and green is the network I'm using to connect to. 

canyouseeme.org with my static IP:

I try to connect using chrome on another network:

 

I enabled windows firewall logging and I can see in my windows firewall log on my Emby server that the connection is being allowed by Windows:

My emby dashboard:

My emby network settings page:

My User settings page:

 

My netstat -a -b -n outputs are below:

 

The emby log files don't show any activity, even in debug mode, when connecting from the remote network. 

 

Thanks,

Rob

 

[Abobader 3464]

Hello robertcrossuk,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Luke 42080]

HI, please attach the emby server log from when the problem occurred:

How to Report a Problem

Thanks !

[robertcrossuk 0]

embyserver (2).txt

Server log attached

[rbjtech 5284]

Thanks for covering all the network basic checks  - everything appears as it should.

Can you do a powershell command :-

from same LAN or routed local network :-

test-netconnection -computername "192.168.86.33" -informationlevel "Detailed" -Port 8096

from WAN/remote :-

test-netconnection -computername "WAN IP or DNS/FQDN" -informationlevel "Detailed" -Port 8096

 

[robertcrossuk 0]

Hello, sorry for the slow reply, details below:

Local Network:

Remote Network (tethered from my cell):

Thanks,

Rob

Edited November 30, 2024 by robertcrossuk
Images didn't attach

[rbjtech 5284]

7 hours ago, robertcrossuk said:

Hello, sorry for the slow reply, details below:

Local Network:

Remote Network (tethered from my cell):

Thanks,

Rob

The 172.20.x.y is RFC1918 private address space that is not your LAN (192.168.86.x) - suggesting you have 'something else' inbetween your PC and the WAN destination.

Could be a dmz, could be a reverse proxy, could be CGNAT, could be a FW, could be a WAF... - but the odd thing is the TCP packet request is getting a valid response.

If you are aware of what the 172.20.10.2 is - then for the moment, you need to remove it for testing.   If emby then works - then you know that is causing the issues.

The SourceAddress can of course be whatever you like (if you used a VPN for example, that would be source) but something 'in the routing/config' here is causing you 'reset' issues - I do not believe this is being caused by Emby itself as a LAN probe works.

Edited November 30, 2024 by rbjtech