New guest account - client trying to connect to LAN IP

[mastrmind11 722]

As the title suggests.  Had a user follow the Emby Connect instructions, and I added the new username as a Guest.  User gets the email, follows instructions, finds server, but is unable to connect because the server is trying to connect via my LAN IP (this is an external user, if it's not obvious).  The admin dashboard is showing the correct WAN IP.

 

Running .70 in a container w/ host mode enabled, if that matters. 

The server is behind a reverse proxy, and external access to the server is working.

I am able to connect via Emby Connect externally via browser and app.

 

Thanks

 

 

[dcrdev 255]

Are you setting the correct host headers on your reverse proxy?

[mastrmind11 722]

Are you setting the correct host headers on your reverse proxy?

No idea, my nginx config is literally a copy/paste of whatever is floating around these forums.  But if they were wrong, how would Connect work?

[pir8radio 1312]

No idea, my nginx config is literally a copy/paste of whatever is floating around these forums.  But if they were wrong, how would Connect work?

 

Yea I think he is going down the correct path, make sure you have the correct headers. like:

        proxy_set_header X-Real-IP $remote_addr;

        proxy_set_header Host $host;

        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

 

is your nginx on the same pc as your emby server?

If so i like to bind emby to 127.0.0.1 it hides the local address from the other apps. 

 

Edited February 15, 2018 by pir8radio

[pir8radio 1312]

Well....   now that i actually think it over lol...   You are right, your emby server should be giving emby connect servers the external IP not your internal IP.... Humm....   I still say try the 127.0.0.1 binding and see if things change, again assuming emby and nginx are on the same box.

Edited February 15, 2018 by pir8radio

[mastrmind11 722]

Yea I think he is going down the correct path, make sure you have the correct headers. like:

        proxy_set_header X-Real-IP $remote_addr;

        proxy_set_header Host $host;

        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

 

is your nginx on the same pc as your emby server?

Yeah, same box.  My config matches that as well as Range $http_range and If-Range $http_if_range

[ebr 16179]

Well....   now that i actually think it over lol...   You are right, your emby server should be giving emby connect servers the external IP not your internal IP.... Humm....   I still say try the 127.0.0.1 binding and see if things change, again assuming emby and nginx are on the same box.

 

It gives them both.  It is possible to use Connect on the local network too and it will use the local address in that case.

[mastrmind11 722]

It gives them both.  It is possible to use Connect on the local network too and it will use the local address in that case.

But is the Guest signup process tied to Connect?  If so, I don't understand how the external client would be getting the LAN IP when Connect externally works just fine.  I just need a place to start digging.  Since my nginx config is correct, could docker in host mode be jacking something up?  As I said, the dashboard shows the correct WAN address.

[Luke 42078]

 

 

but is unable to connect because the server is trying to connect via my LAN IP (this is an external user, if it's not obvious).

 

This is not the reason why it can't connect because it will always try the LAN IP, and then automatically switch to the external address if it fails.

[mastrmind11 722]

This is not the reason why it can't connect because it will always try the LAN IP, and then automatically switch to the external address if it fails.

I get that, but which address should be displayed on the Emby server icon on the device's pick server screen?  Right now it's displaying my LAN address.

Edited February 15, 2018 by mastrmind11

[ebr 16179]

I get that, but which address should be displayed on the Emby server icon on the device's pick server screen?  Right now it's displaying my LAN address.

 

That display will probably always show the local address (just to help you identify the server) but that has no bearing on how it is connecting.

[dcrdev 255]

I just tried this - don't normally use connect and it's just showing whatever I changed the server name to (the pencil icon on the dashboard) , so assuming if you don't set that it defaults to the local ip.

[Luke 42078]

It doesn't default to local, it attempts local first, then switches to external if it fails to connect.

[ebr 16179]

It doesn't default to local, it attempts local first, then switches to external if it fails to connect.

 

Pretty sure dcrdev was just referring to the display.

 

I think the bottom line here is Mastrmind made an assumption about his problem (that it was failing to connect because it was only using the local address) based on the display.  This is not a correct assumption though and the real problem is just that the app is not able to connect via either method.

[Luke 42078]

Right I see, thanks for the clarification.