MrPaulo 7 Posted April 29 Share Posted April 29 (edited) Hi Luke, On Android TV clients (Nvidia Shield) I get the following message "There seems to be a problem accessing your server. Ensure it is running and the network is available" when opening the app. the message dissapears after a few seconds and the apps seems to work to perfection. I don't understand why the message is appearing. I just realised this was happening earlier in the year. Emby client version shown on nvidia shield: "2.1.10g Registered" The message does not appear when I open the emby client on a Samsung Android phone. Version: "Emby for Android 3.3.77" Server is running on a docker container on a synology box (DSM7.2). Emby server version: "4.8.5.0". Unsure this additional information is of any use - I am (and have always been) running a synology ssl reverse proxy (synology manages the certificates via lets encrypt) - works to perfection. I treat my local network as untrusted - everything goes over ssl - local and remote access. Everything works fine either in the local network or external access. I am just wondering if that message relates to anything that is misconfigured / related to a recent version of the server/apps. Or any changes I need to the setup. Thanks. Best regards, Paulo Edited April 29 by MrPaulo Link to comment Share on other sites More sharing options...
Q-Droid 670 Posted April 29 Share Posted April 29 My guess: The Emby server advertises its presence on the LAN which the shield might be detecting. But if you're not allowing non-TLS local connections then it has to fall back to a "remote" TLS connection. 1 Link to comment Share on other sites More sharing options...
MrPaulo 7 Posted April 29 Author Share Posted April 29 I have had Emby running for a long time. this must have been after an update. It is only on the Shield. Android phones, iOS or Mac app (Mac app version 2.2.16) don't show this while on the same network. I have the emby service on a container. This container is on a synology on a remote location.The connection is via https public internet obfuscated by a private sub domain name. Both LANs have a WAN hardware intranet routing to the remote site but the internal IP address and port is different from the external exposed https dns name/IP/port. This internal routing is for other services such as SMB and intranet only sites hosted on the synology box not exposed to the internet. I am unsure how the non-TLS local connections could hop to a new subnet - these are routed, not bridged. Link to comment Share on other sites More sharing options...
Q-Droid 670 Posted April 29 Share Posted April 29 Ah, well that's different. What does the Emby server dashboard show for In-home LAN access? Is it different from the subnet the Shield is on? If the same then you can change that local IP address in the Emby server Network settings to something different. Then the Shield should always treat the server as remote. Do you have anything in the LAN networks field? But if that's not it then the devs might know what causes the warning. The Shield ATV app is different from the Android mobile app. 1 Link to comment Share on other sites More sharing options...
MrPaulo 7 Posted April 29 Author Share Posted April 29 (edited) Thanks. I have the following on the LAN fields: - Lan network: The Synology loopback network xxx.xxx.xxx.xxx/24 - Local IP address: Blank - Local http port number: this is the port that the reverse proxy picks up - this is the only port I have mapped out of the docker container - Local https port number: this is the port exposed to the internet - This never leaves the docker container as I do not have it mapped anywhere In addition these are set: - Read proxy headers to determine client IP addresses - set to "Only when they contain remote network addresses" - Secure connection mode: "Handled by reverse proxy" Edited April 29 by MrPaulo Link to comment Share on other sites More sharing options...
Q-Droid 670 Posted April 29 Share Posted April 29 What about the dashboard LAN IP addr? Link to comment Share on other sites More sharing options...
MrPaulo 7 Posted April 30 Author Share Posted April 30 Hi, The Dashboard shows: - Intro to ports: Running on http port aaaaa, and https port bbbbb - In-Home (LAN) access:: The Synology internal IP address that is bridged to the remote lan in the notation http://xxx.xxx.xxx.xxx:aaaaa - Remote (WAN) access: the dns subdomain and port in the notation https://xxxxxxx.xxxxxxxx.com:bbbbb Link to comment Share on other sites More sharing options...
MrPaulo 7 Posted April 30 Author Share Posted April 30 47 minutes ago, MrPaulo said: Hi, The Dashboard shows: - Intro to ports: Running on http port aaaaa, and https port bbbbb - In-Home (LAN) access:: The Synology internal IP address that is bridged to the remote lan in the notation http://xxx.xxx.xxx.xxx:aaaaa - Remote (WAN) access: the dns subdomain and port in the notation https://xxxxxxx.xxxxxxxx.com:bbbbb Forgot to mention: In-home (Lan) access is not used. in the docker container I have the aaaaa port remapped to a separate port for the reverse proxy to pick it up, meaning that the synology reverse proxy picks this up for the https proxy. the reason for this is that I do not want to allow any http connections - I treat the lan as untrusted - the http packets on port aaaaa should never leave the synology box to the lan. As a point of attention: this is working fine today even on the nvidia shield android tv apps. it has been working fine for a long time. it is just an inconsequential error message that only appears on two nvidia shields that are in their own remote locations. All Android and ios phones on any subnet or from any remote location do not get this error message. I suspect it is something exclusive to the android tv app (as it is only exhibiting the simptom in the android tv app), not the emby server configuration hence this thread. Link to comment Share on other sites More sharing options...
Q-Droid 670 Posted April 30 Share Posted April 30 7 hours ago, MrPaulo said: - In-Home (LAN) access:: The Synology internal IP address that is bridged to the remote lan in the notation http://xxx.xxx.xxx.xxx:aaaaa What I'm trying to establish is if this IP address appears to be on the same subnet as the Shields that throw the warning. Not concerned with how your network is setup, would the Shield consider the IP to be on the LAN. This value comes from the Local IP Address field and is advertised to apps when they connect. The value for IP address here can be anything you want that works for you, it doesn't control bindings. Link to comment Share on other sites More sharing options...
MrPaulo 7 Posted April 30 Author Share Posted April 30 Hi Q-Droid, Thanks. They are not in the same subnet. Link to comment Share on other sites More sharing options...
Luke 37250 Posted May 3 Share Posted May 3 Hi. Can you try searching for our standard android app (Just "Emby" on Amazon and "Emby for Android on Google) on the same device's app store and see how that compares? Thanks. Link to comment Share on other sites More sharing options...
MrPaulo 7 Posted May 5 Author Share Posted May 5 On 03/05/2024 at 20:39, Luke said: Hi. Can you try searching for our standard android app (Just "Emby" on Amazon and "Emby for Android on Google) on the same device's app store and see how that compares? Thanks. Hi Luke, The standard Android version does not display the message. in iPhones, Windows and Samsung phones the message does not appear. Seems to be the one for Android TV only. I only have nvidia shields. I cant say if it is Nvidia shield specific or generic. This is cosmetic - the app works perfectly fine. Thanks. Regards, Paulo 1 Link to comment Share on other sites More sharing options...
Luke 37250 Posted May 5 Share Posted May 5 OK we'll look into it. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now