Updated to 4.5.4.0 now WAN connection is broken

[denywinarto 5]

My server has2 NIC, NIC A is private, NIC B is public and is used for emby remote.

It was rebooted because of blackout, now emby is updated to 4.5.4.0

Now WAN remote access keeps pointing to NIC A no matter what option i change on network menu.

It used to work before blackout and pointed to nic B instead.

I know this isnt port forwarding issue cause my blue iris' webserver on the same server still works correctly.

is there any way to force emby to bind to specific NIC? 

I have tried blocking port 8096 on NIC A but emby still points at A

Edited December 30, 2020 by denywinarto

[Luke 42080]

Hi, nothing changed with this recently, but you can always customize the WAN address in server network settings if needed. Please note that in most cases, it's not needed.

Have you taken a look at this?

https://whatismyipaddress.com/

Emby Server uses services similar to that to detect your wan ip.

[denywinarto 5]

1 minute ago, Luke said:

Hi, nothing changed with this recently, but you can always customize the WAN address in server network settings if needed. Please note that in most cases, it's not needed.

Have you taken a look at this?

https://whatismyipaddress.com/

Emby Server uses services similar to that to detect your wan ip.

By this you mean network > external domain correct? 

Odd i gave it my noip domain address and not working,

i have set noip domain address and on my windows machine the duc client is pointing to the correct nic (nic b) and its giving B ip address as well.

Whatismyaddress is giving A ip address but its intended to be that way cause B has limited bandwidth

[Luke 42080]

Just now, denywinarto said:

By this you mean network > external domain correct? 

Odd i gave it my noip domain address and not working,

i have set noip domain address and on my windows machine the duc client is pointing to the correct nic (nic b) and its giving B ip address as well.

Whatismyaddress is giving A ip address but its intended to be that way cause B has limited bandwidth

What does "not working" mean?

[denywinarto 5]

1 minute ago, Luke said:

What does "not working" mean?

I cant access it from external network using that domain name.

It used to be accessible, but emby WAN was pointing at the B nic and i didnt even need to set domain address on emby.

[Luke 42080]

Ok, I would suggest checking out our Connection Troubleshooter:

https://support.emby.media/support/solutions/articles/44001849007-connectivity

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

[denywinarto 5]

5 minutes ago, Luke said:

Ok, I would suggest checking out our Connection Troubleshooter:

https://support.emby.media/support/solutions/articles/44001849007-connectivity

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

Internal access from another LAN machine works. Only extenal is broken.

Port forwarding cannot be the issue because blue iris' web server works.

Again i think the issue is emby's WAN address is pointing at the wrong interface. And i cant set it to the correct interface.

I also tried putting interface's IP on network > domain name but still no luck

 

Edited December 30, 2020 by denywinarto

[Luke 42080]

Quote

emby's WAN address is pointing at the wrong interface

Emby doesn't actually point at any interface. The system handles dns resolution. I think you are jumping to a conclusion here by zeroing in on Emby as the source of the problem. Is blue iris using the same public facing port as Emby Server? Port forwarding could still be the problem. I think the first thing you want to do is figure out how far the traffic is getting. My guess is that it's never even reaching Emby Server due to network configuration.

[denywinarto 5]

Its using different port. But If emby doesnt choose interface why is it showing specific ip address on dashboard > WAN address ? 

I will check again my modem setting but there should be nothing changed since last time its working correctly.

Other explanation probably my windows machine prioritize nic A after reboot as default nic (wrong nic for emby) 

There is also metric option on nic. But i cannot use it cause i would need to change alot other apps' nic priority and thats even more troublesome.

 

 

[denywinarto 5]

I just checked the log and apparently emby pings to my wrong interface first, then my correct interface second.

112.118.0.200 > wrong nic

112.118.200.200 > correct nic

 

2020-12-30 12.40.20.386 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.1492753 seconds
2020-12-30 12.40.20.386 Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint
2020-12-30 12.40.20.387 Info App: Loading data from Z:\Programs\Emby\programdata\data\connect.txt
2020-12-30 12.40.20.388 Debug App: Ping test result to http://112.118.0.200:8096/system/ping. Success: True
2020-12-30 12.40.20.389 Info App: Loading data from Z:\Programs\Emby\programdata\data\wan.dat
2020-12-30 12.40.20.391 Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.0048124 seconds
2020-12-30 12.40.20.391 Info App: Core startup complete
2020-12-30 12.40.20.391 Info App: Post-init migrations complete
2020-12-30 12.40.20.391 Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding
2020-12-30 12.40.20.392 Debug App: Ping test result to http://112.118.200.200:8096/system/ping. Success: True
2020-12-30 12.40.20.392 Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.0009376 seconds
2020-12-30 12.40.20.392 Info App: Starting entry point Emby.Security.PluginSecurityManager
2020-12-30 12.40.20.392 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 2.22E-05 seconds
2020-12-30 12.40.20.392 Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint
2020-12-30 12.40.20.392 Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 6.16E-05 seconds
2020-12-30 12.40.20.392 Info App: Starting entry point Emby.Webhooks.WebhooksEntryPoint

 

Even when i set the remote address to my noip domain its still doing this after emby restart.

And its showing the ip of 112.118.0.200 on my dashboard

[denywinarto 5]

Can anyone with working remote access run netstat -an ?

Mine shows only this for 8096

0.0.0.0:8096 

Could explain why it wont work

I looked up blueiris port on that list and it's correctly tied to NIC B. E.g

Nic B:443

 

Edit : setting NIC B on emby's local ip address option outputs this :

NIC B : 8096 TIME_WAIT

What does that mean?

FYI I'm running emby in portable mode on another drive, not C.

 

 

Edited December 30, 2020 by denywinarto

[denywinarto 5]

9 hours ago, Luke said:

Emby doesn't actually point at any interface. The system handles dns resolution. I think you are jumping to a conclusion here by zeroing in on Emby as the source of the problem. Is blue iris using the same public facing port as Emby Server? Port forwarding could still be the problem. I think the first thing you want to do is figure out how far the traffic is getting. My guess is that it's never even reaching Emby Server due to network configuration.

I think something is wrong with my installation Luke, 

I tried ping from another machine and i got this

PS C:\Users\Home>  Test-NetConnection noipdomain -port 8096
WARNING: TCP connect to (NIC B IP address: 8096) failed

ComputerName           : noipdomain
RemoteAddress          : NIC B IP address
RemotePort             : 8096
InterfaceAlias         : Ethernet
SourceAddress          : 192.168.100.14
PingSucceeded          : True
PingReplyDetails (RTT) : 3 ms
TcpTestSucceeded       : False

But same test for Blue iris port works

PS C:\Users\Home>  Test-NetConnection noipdomain -port 443

ComputerName     : noipdomain
RemoteAddress    : NIC B IP address
RemotePort       : 443
InterfaceAlias   : Ethernet
SourceAddress    : 192.168.100.14
TcpTestSucceeded : True

 

- Firewall is off on both server and modem.

- Same Port forwarding method for blue iris port works correctly, I'm only using modem > emby server directly to simplify things, no other router.'

[img]https://i.imgur.com/Q2A4Uwi.png[/img]

- I used forcebindip on embyserver.exe so that WAN Address is pointing at NIC B but remote still wont work

- setting NIC B on emby's "local ip address" option and netstat -an outputs this :

NIC B : 8096 TIME_WAIT

- Accessing using NIC B's IP doesnt work either so problem is not on noip ddns

This is getting frustrating, do you think it has anything to do with portable installation?

 

 

Edited December 30, 2020 by denywinarto

[denywinarto 5]

Problem solved, had to restart the modem. Probably something got stuck when i reboot the server. thanks anyways Luke

[Luke 42080]

Thanks for the feedback.