Emby server not reporting WAN address to Emby Connect (only LAN)

[akawoz 12]

Guys, am I missing something? When my guests (or I) login to app.emby.com and signin with connect usernames we only see the LAN address of the server and not the WAN address.

 

My Emby admin account is linked to my Emby Connect username. I've tried unlinking and re-linking the ID but no luck. Anyone have any ideas what is going on here?

 

Also as an aside - is there a way of hiding the actual address and port numbers from the select server screen (instead replace with aliases)?

 

EDIT: I should say that I have a static IP address which I've tried both with and without filling this into the External WAN Address field; regardless the server is detecting it correctly.

 

 

 

 

 

 

 

Edited September 22, 2015 by akawoz

[Luke 37250]

Nothing to worry about. It only shows the last address that was used to connect. Maybe I will just remove that text prevent similar questions going forward.

[akawoz 12]

thanks Luke does that mean I need to give my guests the actual address and port of the server for them to connect to - I thought Emby Connect was meant to take care of that for me?

[danielpugh 2]

It confused me, but worked fine

[Luke 37250]

No, just carry on letting them use Emby Connect as they currently are.

[akawoz 12]

my guests are telling me that when they click on the blue server box (with the LAN address showing) they get a connection failed error message, but if they manually enter the WAN static IP and port in the Add Server dialog then it connects fine:

 

Edited September 22, 2015 by akawoz

[Luke 37250]

could be https related. try disabling the setting to report https as the external address. also, check your server log make sure there are no failures on your server to report info to our servers.

[akawoz 12]

OK, tried disabling HTTPS but no change in behaviour. Here's a server debug log after a fresh start of Emby. Still trolling through it but I find no mention of my static IP address (203.*)

 

http://pastebin.com/pSKgxntN

 

EDIT: later version of the log: http://paste2.org/O6IBcdhg

Edited September 22, 2015 by akawoz

[akawoz 12]

OK this appears to have been solved by me using Full NAT instead of DNAT on my Sophos UTM. More investigation is required. Thanks all