Remote (WAN) Access Stopped Working

[Joe Farmer 2]

Hi all,

 

My remote connection has stopped working and I have tried everything I can think of to get it working again with no success. The only thing that has changed anywhere on my network is my Remote (WAN) access IP changed some time in the last 24 hours for reasons unknown to me, since then I can't get a remote connection.

 

I have a D-LINK DSL-2888A which has a Virtual Server setup for port forwarding as below:

 

Status Name   Local IP           Protocol External Port   Internal Port   Interface   NAT Loopback
HTTP              192.168.1.12   Both       8096                8096               ALL          Off

 

Previously this was all that was needed but now that isn't working. I had had troubles with remote access in the past when rebooting my router as my PC's IP would change but I figured out pretty quickly that I just had to change the Local IP above for it to work again. That is not the issue this time.

 

I have rebooted my router and done a factory reset to be sure there is no router issue and then setup the above virtual server again, that didn't work.

 

I have also tried setting up Port Triggering as below as that is what D-LINK support pointed me to but that hasn't worked either:

 

Number   Name   Interface   Protocol     Triggering Start Port   Triggering End Port   Open Start Port   Open End Port 

1              Emby   PTM0        TCP/UDP   8096                          8096                           8096                   8096                 

2              Emby   ATM0        TCP/UDP   8096                          8096                           8096                   8096 

3              Emby   Eth0          TCP/UDP   8096                          8096                           8096                   8096 

 

I have run an anti-virus scan and found nothing. I have also checked the Inbound Rules in Windows firewall which look fine to me but I don't really know what I should be looking for there. There is one for Emby Server which is UDP and one for embyserver.exe which is TCP. 

 

I have gone through everything https://github.com/MediaBrowser/Wiki/wiki/Connectivity and still no luck.

I am currently working with D-LINK Support but thought I would post this now in case they can't figure it out. 

Latest logs are attached.

embyserver.txt

hardware_detection-63695013592.txt

embyserver-63695013574.txt

Edited June 1, 2019 by Joe Farmer

[rbjtech 5284]

So a few things to check.

a) WAN IP - use 'what's my ip' etc to confirm your WAN IP from the ISP

b ) setup your router port forward from from WAN > your emby local IP, keeping port 8096 (as you did before)

c) ensure the router firewall is also letting through 8096 (usually linked to the NAT process above)

d) for the moment - disable the Windows firewall.

e) use 'canyouseeme.org' to check if Emby's port is now open

f) if this is open, then the issue is with the Windows firewall, so turn the windows firewall back on again and see if you can find the emby firewall rule to check.

g) if the port from canyouseeme.org is still closed - then the issue is the router/firewall config

 

Check Emby WAN config

 

h) in Emby - check that the 'remote (WAN) access is http://your WAN IP:8096 - note not https or 8920

i) if not, then in 'Advanced' check the PUBLIC port numbers are correct and secure connection mode is set to Disabled.

 

I hope that helps.

 

ps - if that works, then also look at setting your PC to a fixed IP and also look at DDNS to dynamically map your ISP WAN IP to a DNS name that emby can then use, then you won't have any future issues when WAN or LAN IP's change 

Edited June 1, 2019 by rbjtech

[Joe Farmer 2]

Note: One thing the D-LINK support guy said is that "the public IP address that you should be getting is different with the IP address of your router." which I assume is referring to the new IP address I see as my Remote (WAN) access IP.

[Joe Farmer 2]

a) WAN IP - use 'what's my ip' etc to confirm your WAN IP from the ISP

   - WAN IP using 'what's my IP' is the same as the Remote (WAN) Access IP shown in Emby

b ) setup your router port forward from from WAN > your emby local IP, keeping port 8096 (as you did before)

   - Not sure what you mean by this? How do I setup port forward from my WAN to my Emby Local IP? Do you mean just having the Virtual Server setup as I already did before? If so then yes, that is done.

c) ensure the router firewall is also letting through 8096 (usually linked to the NAT process above)

   - Not sure how to ensure this? If I go to Firewall Settings on my Router I can Enable or Disable the Firewall and setup Whitelist or Blacklist rules for IP ranges for either WAN->LAN or LAN->WAN. Not sure if I should do that.

d) for the moment - disable the Windows firewall.

   - Done in Windows Defender for Domain, Private and Public networks for the moment.

e) use 'canyouseeme.org' to check if Emby's port is now open

   - Result: Error: I could not see your service on xxx.xx.x.xx on port (8096)

Reason: Connection timed out

f) if this is open, then the issue is with the Windows firewall, so turn the windows firewall back on again and see if you can find the emby firewall rule to check.

g) if the port from canyouseeme.org is still closed - then the issue is the router/firewall config

   - Seems it is an issue with the router/firewall config but what the issue is I have no idea?

 

The only clue I can see is what the D-LINK Support guy said that the Remote (WAN) access IP (119.xx.x.xx) is not the same as the IPv4 IP address my Router is showing (100.xx.xx.xx) which is odd.

[Joe Farmer 2]

h) in Emby - check that the 'remote (WAN) access is http://your WAN IP:8096 - note not https or 8920

   - It is the WAN IP that comes up when I check 'what's my IP' but not what my router shows as the IPv4 IP address

i) if not, then in 'Advanced' check the PUBLIC port numbers are correct and secure connection mode is set to Disabled.

   - Public port numbers are 8096. Secure connection mode was set to 'Preferred, but not required' so I changed it to Disabled but didn't make a difference.

[Luke 42079]

https://github.com/MediaBrowser/Wiki/wiki/Connectivity

 

Which steps succeeded and which ones did not?

[Joe Farmer 2]

https://github.com/MediaBrowser/Wiki/wiki/Connectivity

 

Which steps succeeded and which ones did not?

 

Hi Luke,

 

1) Test Your External Address - Failed

2) Setup Port Forwarding - Failed. Setup as it had always been setup as below with the correct LAN IP:

      Status Name   Local IP           Protocol External Port   Internal Port   Interface   NAT Loopback

      HTTP              192.168.1.12   Both       8096                8096               ALL          Off

3) Verify Public Port - Failed

    - https://canyouseeme.org/ shows the same WAN IP that Emby shows as the Remote (WAN) access IP but fails with the error I mentioned above as below:

    - Error: I could not see your service on 119.xx.x.xx on port (8096)

      Reason: Connection timed out

    - Note: What might be significant is what the D-LINK support guy told me that the IP is different to the IPv4 IP address my Router is showing (100.xx.xx.xx)

 

I also rebooted my router and did a factory reset before trying all of the above again with no success.

 

My internal connection works fine on all devices though.

 

I am waiting for a senior Support Engineer from D-LINK to contact me so hopefully they can figure something out but would appreciate some assistance from you if you can think of anything.

 

I had considered uninstalling and reinstalling Emby server but would like to avoid that if possible as I would have to setup all my libraries again which would take me a very long time to fix up all the meta data of a lot of my media which identifies incorrectly.

[pmurphy0881 12]

I would start by doing a few things.

 

1.) go to https://whatsmyipaddress.net/ and verify that your public ip address is the same that the router sees.

2.) If different then I would try the ip address that's identified there.

3.) If that doesn't work, I would also check your firewall on the server to see that there are rules setup to allow traffic in on the ports that you are using for your server.

4.) if that works then I would look at setting up a ddns service for your server so that you can just use a domain name instead of having to update your IP each time.

[Joe Farmer 2]

1.) go to https://whatsmyipaddress.net/ and verify that your public ip address is the same that the router sees. - It's the same as the Remote (WAN) access IP in Emby (119.xx.x.xx) but not what my router shows as you can see below. Though I'm not sure if they should be the same?

2.) If different then I would try the ip address that's identified there. - Not sure what you mean by "try the ip address that's identified there" but if you mean try to connect that the router IP externally ie. 100.xx.xx.xx:8096 I have tried that and it doesn't work. https://canyouseeme.org/ also shows the 119.xx.x.xx IP that is in Emby and https://whatsmyipaddress.net/.

3.) If that doesn't work, I would also check your firewall on the server to see that there are rules setup to allow traffic in on the ports that you are using for your server. - There are two inbound rules for Emby and one for Port 8096 as below:

I don't see any outbound rules for Emby or Port 8096 though, do I need outbound rules?

[Joe Farmer 2]

SOLVED!!!

 

Aussie Broadband had opted me in to CG NAT without my permission which lead to port 8096 being blocked on their end. They turned it off and after a router and Emby reboot my remote access is now working again.

 

This topic can now be marked as solved.

[Luke 42079]

Thanks for the feedback !

[rbjtech 5284]

SOLVED!!!

 

Aussie Broadband had opted me in to CG NAT without my permission which lead to port 8096 being blocked on their end. They turned it off and after a router and Emby reboot my remote access is now working again.

 

This topic can now be marked as solved.

 

Many ISP's are doing this now - and it's effectively an ISP using a pool of PRIVATE IP's which is then NAT'd to a single PUBLIC IP - much like your home network does.  For browsing this works ok but if you want to HOST something (such as Emby) then you can't do this - as you found out - as you get their 'PRIVATE' IP allocated, not a real 'PUBLIC' IP.

 

Glad it's sorted.

[Joe Farmer 2]

Many ISP's are doing this now - and it's effectively an ISP using a pool of PRIVATE IP's which is then NAT'd to a single PUBLIC IP - much like your home network does.  For browsing this works ok but if you want to HOST something (such as Emby) then you can't do this - as you found out - as you get their 'PRIVATE' IP allocated, not a real 'PUBLIC' IP.

 

Glad it's sorted.

 

Yeah, I'm glad I called them, figured I would while I was waiting for D-LINK support to get back to me and what do you know, they identified the issue immediately. Obviously they get a lot of people with the same issue. Hopefully this thread can help out other people who have the same issue.

[Guest keithcq71]

i am having this same issue with Google Fiber . So I need a private ip address? 

[Luke 42079]

i am having this same issue with Google Fiber . So I need a private ip address?

 

Please check out our connection troubleshooter:

https://github.com/MediaBrowser/Wiki/wiki/Connectivity

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

[Guest keithcq71]

Thanks . I set up port fowarding on Google Fiber box . Can I change my remote port from 8096? 

[Luke 42079]

If you can do that in Google Fiber, then yes, once you've done that, you can specify the public port in advanced server settings.

[Guest keithcq71]

A coworker told me 8096 gave him issues so he switched to 8081 which I have open on my router . I think I need to open some ports on my Windows Firewall as well to resolve my issues . Whats strange is before this week everything was running great . 

[Luke 42079]

If you don't have a reason to change it then i would just leave it at default.

[Joe Farmer 2]

i am having this same issue with Google Fiber . So I need a private ip address? 

 

First thing I would do is call Google Fibre support and ask them if you have been opted in to CG NAT as I was. If so then changing the port probably won't help as they will be blocking most ports that aren't common ports and you will still have the same problem.

 

A clue to whether you are on CG NAT is to check if your Remote (WAN) access IP in Emby is different to the public IP your router shows as mine was. After they took me off CG NAT and I hard rebooted my router, my PC and restarted Emby it was fixed and the IP's matched.

[Happy2Play 9781]

Yes if you are on a CG NAT there is nothing anyone can do.  You would have to work with your ISP.