Remote access on Emby server not working

[RyanCardoz 4]

Hello all,

Recently decided to change where my server was installed (from Nvidia Shield to mini-pc) and I can no longer access Emby remotely (it says "We're unable to connect to the selected server right now...etc etc". I've tried the following:

• launching the remote access URL (from the Emby Server Network Dashboard) on my mobile while not connected to the Wi-Fi
  • Result: Connection timed out
• did the canyouseemee.org port check. The IP listed is the same as the one listed on the Remote access above however when testing the port.
  • Result: port (8092/8096) Reason: Connection timed out
• logged in to my router and looks as though port forwarding is set up. I tried setting it up again just in case but got an error message (see below)
  • Result: error message: "An existing UPNP mapping overlaps with the entered ports range
• disabled the firewall on my mini-PC and tried the above steps again
  • Result: still no access

Setup details

• Router: Technicolor FXA5000
• Modem: Arcadyan Boost 2.1

The router and the modem have different IP addresses. Would that matter? I'm not 100% sure. If so, would one need to be forwarded to the other? Would love some assistance on how to get this resolved.

Cheers

[pwhodges 2012]

Is the PC's networking set to "public" mode?  It needs to be "private".

You listed port 8092 - did you mean 8920?

Paul

[sa2000 674]

6 hours ago, RyanCardoz said:

Recently decided to change where my server was installed (from Nvidia Shield to mini-pc) and I can no longer access Emby remotely

 

6 hours ago, RyanCardoz said:

Result: error message: "An existing UPNP mapping overlaps with the entered ports range

Is the existing UPNP port forward to the IP address of the PC or the Nvidia Shield?

And is it the default http port for remote access 8096 or are using https with default 8920

6 hours ago, RyanCardoz said:

Setup details

• Router: Technicolor FXA5000
• Modem: Arcadyan Boost 2.1

The router and the modem have different IP addresses. Would that matte

If the WAN/Public IP address on the router is one within the private network range then you probably have Double NAT with the modem acting as a router. You can avoid double nat by having the first device, the modem, in bridge/modem mode. There are other ways to get round double nat - like cascading the port forward from the first routing device to the second and then the real port forward would be on the 2nd device - the router

 

 

[rldsebps 0]

I think you will have to bridge your Modem: Arcadyan Boost 2.1, and open ports 8096 on your modem to be able to access the advisor remotely @RyanCardoz

[serverebps01 12]

I think you will have to bridge your Modem: Arcadyan Boost 2.1, and open ports 8096 on your modem to be able to access the advisor remotely @RyanCardoz

[rbjtech 5284]

7 hours ago, RyanCardoz said:

Hello all,

Recently decided to change where my server was installed (from Nvidia Shield to mini-pc) and I can no longer access Emby remotely (it says "We're unable to connect to the

This is the important part of this message - the user has moved from the Shield to the Mini-PC.  Their remote access previously worked - not sure why people are confusing things with talk of double nat..

So all that needs to happen is the destination IP needs to change from the shield to the Mini-PC.  (Assuming they are on the same network).

So to release the upnp bindings - you need to ensure the shield is no longer acting as an emby server, ensure the mini-pc is now the server instead and then restart the router.

This should re-create the upnp bindings as before, but this time your mini-pc is the destination.

As raised above - ensure the mini-pc has it's network set to private - otherwise the WINDOWS firewall on the mini-pc will be blocking any incoming requests from the router.

[RyanCardoz 4]

9 hours ago, pwhodges said:

Is the PC's networking set to "public" mode?  It needs to be "private".

You listed port 8092 - did you mean 8920?

Paul

Yes, I meant 8920. Oops!

6 hours ago, rbjtech said:

This is the important part of this message - the user has moved from the Shield to the Mini-PC.  Their remote access previously worked - not sure why people are confusing things with talk of double nat..

So all that needs to happen is the destination IP needs to change from the shield to the Mini-PC.  (Assuming they are on the same network).

So to release the upnp bindings - you need to ensure the shield is no longer acting as an emby server, ensure the mini-pc is now the server instead and then restart the router.

This should re-create the upnp bindings as before, but this time your mini-pc is the destination.

As raised above - ensure the mini-pc has it's network set to private - otherwise the WINDOWS firewall on the mini-pc will be blocking any incoming requests from the router.

I think rbjtech is on to something here. I deleted the server app from my Nvidia but didn't really disable it. If it helps, the remote access URL didn't change when I installed the new server on the mini-pc so I think there's additional digging I need to do. I'll post my findings as I come across them. Thanks all!

 

Edit to add: also after further digging, the Technicolor FXA5000 is the Modem with the Arcadyan Boost 2.1 categorized as the wireless access point.

Edited May 14, 2024 by RyanCardoz

[rbjtech 5284]

You can check the upnp 'port forward rule' most likely if you login to your router.   It should be pointing the local IP address of your mini-pc instead.

[RyanCardoz 4]

@rbjtechI restarted my modem and it cleared the old port forwarding (which is odd because I never set it up in the first place). Set up port forwarding as outlined in the documentation and voila! it works. Thanks for the guidance!