Local IP - error?

[smc007i 1]

Hi,

 

I saw a few other posts with people asking about the Local IP value, but none seemed to have my problem.  I know you can use localhost:8096 to find your server, that's not my question.

 

My Local IP address shown on the server system page is not the IP of the machine the server is actually located on, why would this happen? Is it self detecting? I cannot seem to find a setting page to enter a local IP.

 

I've attached the screen shot below, the Windows machine that my server is located on is .10, not .100 (it's always on .10 because I fix the address in my router).  How is this being address determined?  If I click on the address it (obviously) takes me to the wrong place that doesn't work - there is another device with .100 on my network.  If I click the remote access link there is no issue and the server can be reached - I use no-ip.com to run a hostname.

 

The only reason I started looking at this was because my Roku channel couldn't connect to my server on my local network and I had to manually enter the IP address of my machine and then there was no further issue and the server could be found.  I wondered if this incorrect local IP might have contributed to the Roku's issue.

 

Regardless, how can I get the local IP to show correctly? I cannot find anywhere to set this going through the menus, have I missed it?

 

 

[theniteow1 25]

I just upgraded to 3.0.5800.0 and now I am running into this issue.  It is detecting one of my CableCard Tuners as the main IP Address of the machine.  The IP Address of my server is actually 192.168.1.12, the address you see here is the IP address of the my Hauppauge DCR-2650 tuner (it can be accessed over a network).  Not sure why it's all the of sudden doing this, never ran into this problem before with Emby .  Nothing has changed in my setup, except for the recent upgrade to v 3.0.5800.0.  I had this issue with ServerWMC, and had to hard code the IP Address. Will I need to do something similar?

 

server-63586895820.txt

[theniteow1 25]

I'm running into a similar issue all the sudden.  It is detecting the IP Address of one of my Hauppauge DCR-2650 tuners as the main IP Address of the machine. Trying to determine a resolution, and will post here if I find it.

[jhoff80 94]

For what it's worth I saw similar with a secondary NIC in my server PC.

[theniteow1 25]

This fixed my issue, somehow my bindings got screwed up and my tuner's became first in the priority order.  Once I fixed that, Emby corrected the problem on it's own.  However, it would be nice to figure out a way to hard code an IP Address in Emby as well:

 

http://windows.microsoft.com/en-au/windows/change-network-protocol-bindings-order#1TC=windows-7

Edited December 29, 2015 by theniteow1

[Luke 42078]

I posted a .1 revision to the beta. Please try it out and report back. Thanks.

[theniteow1 25]

I posted a .1 revision to the beta. Please try it out and report back. Thanks.

 

Will do!

[theniteow1 25]

@@Luke Sorry, it's a no go..  I changed my Network Bindings back to what they were, and 3.0.5008.1 still identified one of the tuners as the main network device.

[Luke 42078]

Ok, thanks. Please provide the server log.

[theniteow1 25]

@@Luke Log files for your viewing pleasure....

server-63586977757.txt

server-63586977927.txt

[Luke 42078]

Are any of these addresses incorrect?

http://192.168.235.186:8096
http://192.168.76.234:8096
http://192.168.1.12:8096

[Luke 42078]

The reason i ask is because the http server listens on all interfaces. What I added for this beta to prevent incorrect detection is it rounds up all the available ip addresses and then actually issues test requests to the emby server api

http://192.168.1.12:8096/system/ping

All three of the above succeeded which means emby server is able to receive traffic at that address.

[theniteow1 25]

http://192.168.235.186:8096
http://192.168.76.234:8096

 

So these IP Addresses are the assigned IP Addresses to my Hauppauge DCR-2650 Tuners, so yes in a way they would respond to a ping, and they are valid.  However, they are not the actual IP address of the server, but, they are viewable as actual "network" devices, as seen below:

 

So I don't think a ping would be able to determine if these are valid network devices or not.  Would a tracert maybe better?  Perhaps to see if it's able to talk to the Internet...  Dunno, just throwing out ideas...

Edited December 29, 2015 by theniteow1

[Luke 42078]

Sorry, I should have worded it differently. It's not a ping in the true sense of what you're thinking of. It's a real http request to an actual emby server api url. The fact that it succeeds means that emby server is capable of receiving traffic at that url.

[theniteow1 25]

Sorry, I should have worded it differently. It's not a ping in the true sense of what you're thinking of. It's a real http request to an actual emby server api url. The fact that it succeeds means that emby server is capable of receiving traffic at that url.

 

These tuners have a web interface you can go to see the status, so an HTTP is still going to come back with something.  For example:

 

[Luke 42078]

yea i understand, but what's happening is those devices are not requesting exclusive access for all ports but rather just the ports they need (80). Emby is doing the same for port 8096 and listening for traffic on all available network interfaces. So while it might look odd to see that as the local address it should work just fine.

[theniteow1 25]

yea i understand, but what's happening is those devices are not requesting exclusive access for all ports but rather just the ports they need (80). Emby is doing the same for port 8096 and listening for traffic on all available network interfaces. So while it might look odd to see that as the local address it should work just fine.

 

However, I can confirm it doesn't work.  It will take a long time to find the server, when it does if I try to login on a profile it asks for a password, when no password is required.  Then I am unable to access the library, or Live TV.  Unless I force it to go to 192.168.1.12, it does not work at all.

[Luke 42078]

then please provide a server log of that, thanks.

[theniteow1 25]

then please provide a server log of that, thanks.

 

No problem, I'll have to "break" it again.  Wife is already upset at me for breaking it today, so it will probably be this evening sometime before I can give you logs.

[Luke 42078]

Also please let me know if you see any different behavior in 3.0.5800.2. Thanks.

[theniteow1 25]

Also please let me know if you see any different behavior in 3.0.5800.2. Thanks.

 

Ok, I was able to reproduce it this morning.  Interesting enough this time I could login, but couldn't watch live TV.  Yesterday, I couldn't even login, it would just keep asking for the password.  Here are the logs from this morning.  I didn't upgrade to 3.0.5800.2, wanted to reproduce it first, then I'll upgrade.

server-logs.zip

[theniteow1 25]

Ok, upgraded to 3.0.5800.2, and it exhibits the same behavior.  Interesting enough I can watch Live TV just fine through a web browser, but not through the FireTV.  It seems to be breaking that exclusively for some reason.

server-logs-3.0.5800.2.zip

[Luke 42078]

Ok, upgraded to 3.0.5800.2, and it exhibits the same behavior.  Interesting enough I can watch Live TV just fine through a web browser, but not through the FireTV.  It seems to be breaking that exclusively for some reason.

 

Thanks. When you get 3.0.5803, please try again and provide the server log. Thanks.

[theniteow1 25]

Thanks. When you get 3.0.5803, please try again and provide the server log. Thanks.

 

Yep, will do.

[theniteow1 25]

Ok, better results, but it still didn't identify the correct NIC on one of my servers.  I have two Emby servers, one that only does Live TV only, and one that does my Media Library.  The one with Media Library has two NICs it.  Emby identified the NIC properly on it this time with the new version as before it didn't.  The one with the tuners (my TV Server) still identified one of the tuners as the primary NIC.  It's getting better though.  Here are the logs.

MediaServer.zip

TVServer.zip