Remote access not working, either with upnp or port forwarding.

[castoraman 0]

Hello, I tried Emby in the vacation house of the family and it was working fine.
Back home, I decided to switch to Emby over Plex but so far things are not going so well.

On local network, everything works just fine.

Remotely, I can't manage to connect to the server. I checked many topics with the same issue without success. Is there any known bug ?

 

I tried port forwarding since upnp is not working, no success.

I'd really appreciate to stay on Emby since Plex is missing some choices between 4mbps 720p and 8mbps 1080p. But for that I'd need it working remotely.

embyserver.txt hardware_detection-63755126067.txt

Edited April 27, 2021 by castoraman

[Abobader 3464]

Hello castoraman,

** 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

[rbjtech 5284]

How are you connecting remotely ?  from a web browser it should be http:\\<your WAN IP>:8096

Can you show the port forward on your router ? (remove the WAN address from any screen grabs)

You should be forwarding ANY WAN address on Port 8096 to 192.168.1.31 (according to your log) 

 

[castoraman 0]

30 minutes ago, rbjtech said:

How are you connecting remotely ?  from a web browser it should be http:\\<your WAN IP>:8096

 

Yes that's what I'm doing.

 

Here is my NAT cfg :

 

CLARENCE is my pc, 192.168.1.31

 

In UPNP cfg, Plex is showing up but not Emby.

[rbjtech 5284]

ok - that looks reasonable  - So Assuming emby is running on your PC (Clarence) - I would use it's IP rather than it's name - ie 192.168.1.31

If emby is not running on this PC - then you need to put the IP where it is running.

Other things to check are

1) Windows firewall has a suitable rule to allow incoming traffic (should be setup automatically when you install emby - but worth checking)

2) Security software (Anti-Virus etc) is not blocking the communication.

For a short period, it's worth disabling the above just to check, if it then works, you know where to look next but don't forget to turn it back on

ps - unrelated, but forwarding port 80 from the internet to any local server really is not recommended..

 

 

[Carlo 4561]

Open a command prompt on Clarence PC and type

tracert 8.8.8.8

Take a look at this and tell us after the first line if any of the next 4 lines have an IP that starts with 10, 192, or 172? 

[Carlo 4561]

If not in a web browser on any computer on your LAN go to www.canyouseeme.org and run a test to port 8096 and 8920.

Do they fail or pass?
Is the IP it shows on canyouseeme.org the same IP as shown in Emby Dashboard for your Remote IP?

Make sure you have no VPN services running on the server or client machines.

[rbjtech 5284]

ah yes, our good old friend CG NAT... 

Is there any way to get this check included in the install to warn the user that remote access may not be possible ?  It seems easy enough to test for ?

 

[Carlo 4561]

Just now, rbjtech said:

ah yes, our good old friend CG NAT... 

Is there any way to get this check included in the install to warn the user that remote access may not be possible ?  It seems easy enough to test for ?

 

Funny that you mention that.  I was thinking about that as well.  Was also thinking about a javascript and canyouseeme.org type replacement that would do both check automatically and could be linked to a support article.  The js check wouldn't be foolproof but would solve/find 90% or so of the CGNAT type issues just looking at the hops used.

[castoraman 0]

18 hours ago, rbjtech said:

1) Windows firewall has a suitable rule to allow incoming traffic (should be setup automatically when you install emby - but worth checking)

2) Security software (Anti-Virus etc) is not blocking the communication.

 

Tried to shutdown windows firewall, it's the same. I have no other fw software.

 

18 hours ago, rbjtech said:

ps - unrelated, but forwarding port 80 from the internet to any local server really is not recommended..

 

Ok I removed this rule, dunno what it is since there is nothing under that IP on my network.

 

16 hours ago, cayars said:

Take a look at this and tell us after the first line if any of the next 4 lines have an IP that starts with 10, 192, or 172? 

80, 193, 193 and 193.

 

16 hours ago, cayars said:

If not in a web browser on any computer on your LAN go to www.canyouseeme.org and run a test to port 8096 and 8920.

 

8096 pass, 8920 fails

 

16 hours ago, cayars said:

Is the IP it shows on canyouseeme.org the same IP as shown in Emby Dashboard for your Remote IP?

 

yes

 

16 hours ago, cayars said:

Make sure you have no VPN services running on the server or client machines.

No nothing like that.

 

 

I tried the remote access via my mobile phone, without wifi so with the carrier network, and it's working. Very strange.

[rbjtech 5284]

Yes - the fact 8096 is responding is good - it means your port forward is working and emby is responding.

The other good news is you do not have CGNAT. 

To note - You cannot test an external emby connection internally - unless you have setup some loopback networking.

As you have found out - the best way to test is from a 3G/4G/5G phone with wifi turned off - ie a real WAN internet connection provided by your mobile.

Enjoy

ps - 8920 will only respond if you have setup HTTPS.