Emby Connect is geting in-home address not the remote (WAN) access

[HawkXP71 112]

Recently, not sure when it changed to be honest.  New emby connect connections are failing.

Ive tracked it down a bit, but the clients trying to connect via emby connect, are getting my servers "in-home (LAN) access" url, as opposed to my remote URL.

If i manually set the URL and port, everything is fine.

Is there a setting somewhere on the server that I messed up?

[Luke 42079]

Hi, does your server dashboard display the correct LAN and wan addresses?

[HawkXP71 112]

6 minutes ago, Luke said:

Hi, does your server dashboard display the correct LAN and wan addresses?

Yes, both the address and the port numbers are correct

[HawkXP71 112]

Is there anyway for a server admin, to see what is being sent for emby connect?  Or is that information only on the emby.media side of the world?

[Luke 42079]

1 hour ago, HawkXP71 said:

Yes, both the address and the port numbers are correct

What about the entire addresses?

[Luke 42079]

1 hour ago, HawkXP71 said:

Is there anyway for a server admin, to see what is being sent for emby connect?  Or is that information only on the emby.media side of the world?

It is the values being displayed on the server dashboard.

[HawkXP71 112]

13 hours ago, Luke said:

It is the values being displayed on the server dashboard.

 

13 hours ago, Luke said:

What about the entire addresses?

The url looks correct.  The protocol is http, the address is correct as well is the port

[HawkXP71 112]

14 hours ago, Luke said:

It is the values being displayed on the server dashboard.

Using my phone (not in lan), I am able to log into emby connect, and I see my server.
The url shown is the internal IP address even though I am connected via the cellular network.
When I long press on the server, and view server info, i see the correct WAN address.

However, when I connect,  it appears to be choosing the LAN not the WAN address.

[Luke 42079]

HI, what makes you think it is choosing the LAN address?

[HawkXP71 112]

3 minutes ago, Luke said:

HI, what makes you think it is choosing the LAN address?

When I manually enter the Wan address it works fine. 

 

When I manually enter the lan address I get the same results (it just sits for 30 seconds or so until it times outl

[Luke 42079]

What exactly happens?

[HawkXP71 112]

11 minutes ago, Luke said:

What exactly happens?

It spins and after 20 or 30 seconds. 

Then I get the unable to reach server.  Please ensure it's running and try again. 

 

 

[Luke 42079]

Can you try it again?

[HawkXP71 112]

13 hours ago, Luke said:

Can you try it again?

no change

[sa2000 674]

On 26/11/2024 at 16:22, HawkXP71 said:

When I long press on the server, and view server info, i see the correct WAN address.

The fact that you see the WAN IP address and port here means that the client app would be seeing it as well. 

So when you try this WAN IP and port on the same device using the phone internet browser, it reaches the server ok ?

Is it Emby for iOS or Emby Android app? And what version?

If it is android, there will be some log files you can fetch

On 27/11/2024 at 05:15, HawkXP71 said:

it spins and after 20 or 30 seconds. 

Then I get the unable to reach server.  Please ensure it's running and try again. 

Anything in the server log during this period ?

 

On 25/11/2024 at 18:59, HawkXP71 said:

but the clients trying to connect via emby connect, are getting my servers "in-home (LAN) access" url, as opposed to my remote URL

what clients / apps ? versions ? / browser?

On 26/11/2024 at 00:16, HawkXP71 said:

Is there anyway for a server admin, to see what is being sent for emby connect?  Or is that information only on the emby.media side of the world?

On a remote PC you can you http://app.emby.media in a browser with the Dev Console enabled (F12) and network logging will show what the browser gets back after logging into Emby Connect - the request that goes to Emby Connect is "https://connect.emby.media/service/servers?userId=xxx" - the response will have the server wan and lan ip addresses and ports. Note that if the server does not have https enabled - you will need to try with http://app.emby.media and not https://app.emby.media as you would get CORS errors blocking the http requests to the server.

The browser dev console network logging will show what url's get used to access the server after you select it after the Emby Connect login

 

[sa2000 674]

On 26/11/2024 at 16:22, HawkXP71 said:

It appears to be choosing the LAN not the WAN address.

Could it be that it is using the LAN port with the WAN IP address ? I have encountered something like this on Android and I am looking further into it.

[HawkXP71 112]

On 11/29/2024 at 9:27 AM, sa2000 said:

Could it be that it is using the LAN port with the WAN IP address ? I have encountered something like this on Android and I am looking further into it.

I do not believe that is the case, only because the domain and port of the URLs listed are correct

[HawkXP71 112]

On 11/29/2024 at 9:27 AM, sa2000 said:

Could it be that it is using the LAN port with the WAN IP address ? I have encountered something like this on Android and I am looking further into it.

 

On 11/28/2024 at 2:56 AM, sa2000 said:

The fact that you see the WAN IP address and port here means that the client app would be seeing it as well. 

So when you try this WAN IP and port on the same device using the phone internet browser, it reaches the server ok ?

Is it Emby for iOS or Emby Android app? And what version?

If it is android, there will be some log files you can fetch

Anything in the server log during this period ?

 

what clients / apps ? versions ? / browser?

On a remote PC you can you http://app.emby.media in a browser with the Dev Console enabled (F12) and network logging will show what the browser gets back after logging into Emby Connect - the request that goes to Emby Connect is "https://connect.emby.media/service/servers?userId=xxx" - the response will have the server wan and lan ip addresses and ports. Note that if the server does not have https enabled - you will need to try with http://app.emby.media and not https://app.emby.media as you would get CORS errors blocking the http requests to the server.

The browser dev console network logging will show what url's get used to access the server after you select it after the Emby Connect login

 

When I run off a browser on my phone I get the message "Unable to reach XXXX" but the warning lists both the WAN and LAN 

When I click on the WAN address it works, the LAN fails (as expected)

Mostly from the android app, sometimes from the android for android TV app or other Smart TV apps.  I cant get their versions right now.

The andrioid app on my phone is v3.4.20

I have tried this with all sorts of apps/clients/browsers, and lately I just eventually use the manual connect

When looking at the network dev console, the two URLs look correct.

The URL shown under the server box on the "selectserver.html" page is still the LAN address however.





 

[sa2000 674]

On 02/12/2024 at 20:48, HawkXP71 said:

The andrioid app on my phone is v3.4.20

I have tried this with all sorts of apps/clients/browsers, and lately I just eventually use the manual connect

When looking at the network dev console, the two URLs look correct.

The URL shown under the server box on the "selectserver.html" page is still the LAN address however.

I have encountered an issue where the android app was not using the correct public port. Possibly using an old port rather than current.

Do you have one android device that is having the problem that you could try after deleting the app cache and data and starting afresh for the Emby for Android app? To see if this resolves the issue

(Through Android Settingd / Apps / Emby / Storage)

[HawkXP71 112]

3 hours ago, sa2000 said:

I have encountered an issue where the android app was not using the correct public port. Possibly using an old port rather than current.

Do you have one android device that is having the problem that you could try after deleting the app cache and data and starting afresh for the Emby for Android app? To see if this resolves the issue

(Through Android Settingd / Apps / Emby / Storage)

Most of the issues that brought this up were new installs (hotel room smart tv, fresh install of emby)

Is there a log feature I can turn on for the TV versions/Web versions/android versions (all 3 have shown this issue) that debugs how the decision is made to try the LAN IP vs the WAN IP?

when I manually set it up, (I have a fixed IP and a DNS entry for "emby.XXX.com" to make it really easy to connect to, it works fine.  That address is the same as what is shown on the dashboard, and what is returned (debugging in chome's network call analyzers)

 

[sa2000 674]

4 hours ago, HawkXP71 said:

Most of the issues that brought this up were new installs (hotel room smart tv, fresh install of emby)

I would rather do the investigation of the problem arising with one of your own devices rather than a hotel room

I am not sure how you have determined that it is using the local IP address without having a network packet capture for what is being sent out from the android device. I had a case where View Server Info showed the correct WAN IP address and WAN Port but the android device requests to the server went out on a different port and I could see that becasue that wrong port was an old port and still routed to the server and it actually got to the server and the server debug logging showed the port number used

 

4 hours ago, HawkXP71 said:

Is there a log feature I can turn on for the TV versions/Web versions/android versions 

Emby for Android has logs - if you open up App Settings within the Emby App, you will see a button for Logs within the Emby for Android settings. That displays each log file name and option to open and share the log file with yourself - by emailing it to your mailbox. You can then copy and paste out the text to text files and zip and attach here - together with the Emby Server Logs - which would be good to have debug logging enabled beforehand for the server.

And as it is wan ip address related which are stripped when downloading logs, it would be best if you send me the raw log files by private message in zip files together with the times of the tests and what the public IP was for the android device at the time and what the server wan ip address and port are

See

Emby Server Log Files and Debug Logging Setting

Emby Server Data Folder location

Would be good if you could do this and test it on one of your own android devices after you purge the cache and data of the Emby for Android app and login afresh through Emby Connect

 

 

Edited December 4, 2024 by sa2000

[HawkXP71 112]

Quote

would rather do the investigation of the problem arising with one of your own devices rather than a hotel room

Understood, this was just the first time I had hit the problem mself.

 

Quote

I am not sure how you have determined that it is using the local IP address without having a network packet capture

It was an assumption, based on typing the address in manually and it working fine.  But using the local address by hand gave the same mode of failure.

But yes, it 100% could have been something else in the url that was wrong.

Ill run through the tests tonight and let you know