Cannot access Emby remotely

[ramseyn 15]

Hi

 

My router was recently reset by my ISP during troubleshooting.

I can no longer access Emby remotely.

 

On the NAS I have enabled remote access in NMetwork section

I have enabled Remote Access under two user accvounts

I have set up a port forward rule on the router

ShieldsUp now shows the port (8096) as open.

Ping gets no response

 

Attempts to connect through my WAN address result in Emby reporting it is trying to connect to an old instance on another server (at least, the server name is the old server). The old server is at an IP that is not set up in port forwarding.

Only the current server is in the port forwarding.

 

If I look at emby.media it shows only my current server. In emby client apps the old server is present as well and I cannot delete it from the list.

the documentation talks about Emby Connect but I don't believe I am using this as I have no idea of my Emby Connect name and I cannot find it in my Emby account.

So I am just using my WAN address and port number 8096.

 

I used to be able to access using just the IP and port...

 

 

embyserver (7).txt

[Luke 42743]

Quote

Attempts to connect through my WAN address result in Emby reporting it is trying to connect to an old instance on another server (at least, the server name is the old server).

Hi, what makes you think this?

How did you setup port forwarding in your router?

[ramseyn 15]

8 hours ago, ramseyn said:

I have set up a port forward rule on the router

See above re port forward.

Rule says incoming WAN traffic on port 9096 should go to Nimbustor4 on port 9096.

My NAS is called Nimbustor4. The old one is Nimbustor2.

When I try to access my WAN address Emby says "Nimbustor2" at the top of thecscreen when asking for username and password although Emby is turned off on that NAS and the port forward is to Nimbustor 4

Edited Wednesday at 10:24 PM by ramseyn

[Luke 42743]

Hi, can you show a screenshot of your port forwarding? Thanks.

[ramseyn 15]

With pleasure.. 

[Luke 42743]

Are you sure that device ip address is still correct?

[ramseyn 15]

Yes. I can ping it locally and use emby locally.

[ramseyn 15]

Edited

 

Edited 20 hours ago by ramseyn
Remove remote IP

[Neminem 1782]

@ramseynedit or delete that image, we can see your remote IP.

[ramseyn 15]

14 minutes ago, Neminem said:

@ramseynedit or delete that image, we can see your remote IP.

Good point! Thanks!

[Luke 42743]

what happens when you're outside of home and you put the remote address into your browser address bar? you can test this on a smart phone by disabling wifi.

[ramseyn 15]

That's how I've been testing it. Nothing happens. On a Windows PC I get "nn.mmm.xxx.yyy refused to connect."

where that us my external address

Edited 13 hours ago by ramseyn

[Luke 42743]

You may just want to check and make sure that you have never restricted remote access inside the server in any way. If you're not sure, the server log from when you attempted that will tell us.

After that please step through our Connection Troubleshooter:

Connecting from Client Apps

Please let us know which steps succeed and which ones do not. Thanks.

[ramseyn 15]

As I have said, internal works fine so that section of the linked article is a Tick.

I have also confirmed that Remote Access is enabled both in the Networks tab and for 2 users.

Enable automatic port mapping is enabled.

I have tried it disabled as well as the article says turn off if it doesn't work and a manual port forward is defined. It doesn't work either way.

UPnP is enabled on the router.

Server IP is static (and as a precaution also reserved in the router).

I only have one router.

FYI I have a static public WAN address.

I am not running a VPN.

Remote access fails on Windows machines with firewall turned off, and on my phone (which used to work).

Tracert to google DNS servers shows no 172.x.x.x/24 devices in the route.

 

I cannot find my EmbyConbect ID - its not shown anywhere I can see when I log in yo emby.media (which just brings me to the foruns).