Cannot access server remot

[MunchkinDaddy 2]

I got a new computer, new WiFi Router and New Mesh Wifi and for some reason since I got the new equipment; I have not been able to access Emby remotely outside my home network. I've tried on Android Phone, Android Auto and on a Desktop PC and no luck. I've checked everything I can think of and cannot access it outside of home network. I have Emby Premiere. I've checked my firewall on home PC (that hosts the server) and the app is allowed through. I also have inbound and outbound rules set for the ports for Emby to allow. I have Port Triggering set up for the ports on the router as well as port reservation set up on the mesh wifi for the ports. Every thing I can think of; and I just can't get into it remotely. Is there a setting somewhere that I can see what is blocking the access or can someone help? It's not a deal breaker if I can't access it outside of home network; but I would prefer to be able to access just in case. 

[pwhodges 1855]

If the new computer is running Windows, check that the networking mode is set to "Private" instead of "Public".

Paul

[MunchkinDaddy 2]

I didn't think of that, thanks; let me try it

[Luke 40111]

Please let us know if that helps. Thanks.

[MunchkinDaddy 2]

Unfortunately it didn't help. Tried it on an android phone, android auto and windows PC and still can't get in. It comes up with the Select Server screen and when I click on the server it says its not available. 

[Luke 40111]

@MunchkinDaddyI would suggest checking out our Connection Troubleshooter:

Connectivity

Please try the steps listed there and let us know which ones succeed and which ones do not. Thanks !

[MunchkinDaddy 2]

Tried everything including using a phone with wifi off and using the remote address on a web browser; still cannot connect to it. When using the data from the phone I alos tried connecting to the Emby App on the phone and the Emby for Android App on the phone and neither would connect with the wifi off on the phone. Once I had the wifi on on the phone; both the apps connected right away to the server. 

[pwhodges 1855]

Was the new equipment because you have a new ISP?

Paul

[MunchkinDaddy 2]

Didn't change ISP. Was time for new equipment so I upgraded on my own. 

[Luke 40111]

Have you setup port forwarding in your router? You may need to go into the router settings and adjust the port forwarding rules for the new server machine.

[MunchkinDaddy 2]

Yes I have. I have created to new port forwarding for both the router and the mesh wifi. I've tried accessing it on just the router SSID and the mesh SSID and neither worked. 

[Luke 40111]

How did you set it up?

[MunchkinDaddy 2]

[mik8451 2]

This doesn't look right to me. Surely you should forward external port 8096 to internal port 8096. Port 8920 is for https connections only, and if you use it, then external port 8920 should map to internal port 8920. Have you checked that your port 8096 is connectable using https://canyouseeme.org/ and ensure that you put 8096 as the port?

[MunchkinDaddy 2]

I figured external and internal ports were supposed to be different ports. I'll give it a shot

[Luke 40111]

7 hours ago, MunchkinDaddy said:

I figured external and internal ports were supposed to be different ports. I'll give it a shot

HI, please let us know if it helps. Thanks.

[MunchkinDaddy 2]

Tried adjusting both the http and https and it didn't help at all. I get to the screen whee I can pick the server so it sees the server, just won't connect to it. 

[mik8451 2]

Are you using the correct public ip address, as identified by whatismyip.com? Just thinking that unless your isp provides a static public ip address (usually an extra cost), then you are not guaranteed to have the same public ip address next time you connect to your isp. The usual fix for this is to use a dynamic dns service (DDNS), which is often set up using your router, so maybe this is what is missing? 

I suspect that seeing the server may be cached, so not necessarily certain. Did you confirm that the port is contactable as recommended using https://canyouseeme.org/?

[MunchkinDaddy 2]

I didn't get a chance to check if the port is contactable. Will have to check later to see if there is a ddns 

[mik8451 2]

You don't have to have a dynamic dns, but you will need to check what the public ip address of your server (whatismyip.com) is before attempting to connect. Most UK isp's (Sky, EE etc) either charge extra for a dedicated public address or don't offer one at all. This is when a dynamic dns helps - it checks what the public ip is and periodically updates a server that you have registered with so you can use a name eg myembyserver.myddns.org or something similar instead of an ip address. As far as I know the ddns can be run from the server or from the router.

 

The connectivilty checker I referenced earlier will show you what the public ip address is, so if that gets a successful reply on port 8096 it means that Emby server is running and listening on port 8096, and your port forwarding is correctly set up. 

Hope this helps, sorry if I'm telling you something you already know.

[Luke 40111]

11 hours ago, MunchkinDaddy said:

Tried adjusting both the http and https and it didn't help at all. I get to the screen whee I can pick the server so it sees the server, just won't connect to it. 

Hi, adjusting how? What exactly did you do?

[MunchkinDaddy 2]

I set a Port Forwarding for Port 8096 with the External and Internal Port being 8096 and the device IP address as the In Home Lan Access IP (which is the In Home Lan IP). I have another Port Forwarding set for port 8920 set up the same way. If I try to change the IP to the remote WAN access IP, I get an error from the router saying that the IP address and LAN IP should be in the same subnet. I also checked canyouseeme and neither 8096 or 8920 ports can be seen on the Remote Wan IP. I wont check those ports for the In Home WAN. Hopefully this provides the information you need to help. 

[Luke 40111]

@MunchkinDaddycan you show screenshots of your router port forwarding options? Thanks !

[MunchkinDaddy 2]

Sent them in a message

[Luke 40111]

@MunchkinDaddyare you sure the ip address you used in your port forwarding rules is correct? Does your ISP use a CGNat? Have you checked for that? 

https://www.purevpn.com/blog/how-to-check-whether-or-not-your-isp-performs-cgnat/

Because if they do, then you'll need to use a VPN or TailScale for remote access.