Unable to connect from Android phone or Android TV (Shield)

[buzzra 3]

People were able to connect to my Emby server earlier today, from their Nvidia Shields, using Emby Connect, but now it is not working. In testing I tried from my Android phone and it does not work either. when I try to log in at app.emby.media it also tells me it cannot connect to the server. I am able to use a browser and manualy put in the hostname with no problem. I updated the apps on both platforms and it still didn't work.

 

edit: I am running server version 4.1.1.0 via Docker and Nginx reverse proxy.

 

Thanks for the help

 

buzz

Edited July 26, 2019 by buzzra

[ebr 16184]

Hi. Make sure nothing is blocking your server from getting out to update information on the internet.

 

Does the WAN address shown on the dashboard match what you made work manually?  Has this changed recently?

[buzzra 3]

Hey ebr, thanks for the help. 

 

The WAN address shown on the dashboard is not quite the same as what works manually. What works manually is https://emby.mydomain.net. What shows on the dashboard is https://mydomain.net:8920.  As it is behind the reverse proxy, the proxy uses standard SSL port 443 and the hostname part of the URL to redirect to the 8096 port of the container running Emby. I have a static IP address, and my own domain, so this has not changed

 

This has all been working for a while, and earlier in the day yesterday, and then suddenly didn't work in the evening. The server also went away from the app.emby.media screen and I cannot add it back with https://emby.mydomain.net, as it was before. It immediately comes back with, "We're unable to connect to the selected server right now. Please ensure it is running and try again." The server is up and can be contaced from a browser off of my local network using https://emby.mydomian.net. The server has been upgraded to 4.2.0.40, but I still cannot add it to Emby Connect.

 

All of the URLs above are generic , but the same format as my actual URL. 

 

Thanks again for any ideas on what might be happening.

 

buzz

Edited July 27, 2019 by buzzra

[Luke 42079]

Hi, in order for you to be able to use Emby Connect, the addresses on the server dashboard will need to be correct. It sounds like you need to configure the public facing port(s) in advanced server settings.

[buzzra 3]

There are no public facing ports behind a reverse proxy. They are reverse proxy facing.

 

Everything was working a few hours before it just stopped and the server was removed from Emby Connect. It had been working for weeks. Nothing changed except the update of the Android clients and the server. Now I can get to my server from anywhere in the world via a browser and a simple URL, but I cannot add the server to Emby connect with that same URL. 

 

Is there a way to set the ports in advanced settings that will turn off HTTPS? That is all being handled by the reverse proxy and it only talks to the Emby server via HTTP on the internal Docker network that is never exposed. It won't let me leave the HTTPS port fields blank. I also have the secure connection mode set to "handled by reverse proxy". 

 

I changed the advanced settings so the dashboard has the same URL as what works from a browser. Still no go because I still can't add the server to Emby Connect.

 

buzz

[Luke 42079]

There's always a port even if it is just the default. It sounds like you want to set 443 as your public facing port number. Once you do that, the address reported to Emby Connect will be updated to match.

 

 

 

Still no go because I still can't add the server to Emby Connect.

 

Why can't you do that? What do you mean by this?

[buzzra 3]

@@Luke,

 

Sorry for the confusion. I could not leave the HTTPS port blank. I did set it to 443 and it still does not work. 

 

When this started, the server disappeared from Emby connect. I did not delete it. Now I can't add it back even with the correct URL showing on the dashboard. When I try I get "We're unable to connect to the selected server right now. Please ensure it is running and try again." The server is running and the URL works from a browser outside of my network. 

 

Again, this was working in the morning and not in the evening. Had been working for weeks with my original settings. The only changes were the Android apps and the server were updated. If the settings were wrong, why did it work for so long?

 

buzz

[Luke 42079]

What about on app.emby.media?

[ebr 16184]

You followed the process outlined here: https://emby.media/community/index.php?/topic/75801-emby-on-google-home-i-cant-reach-your-emby-server/?p=768097?

[buzzra 3]

@@Luke, That is what I mean. The server disappeared from app.emby.media. It was NOT deleted, just disappeared. When I try to add it back on app.emby.media I get "We're unable to connect to the selected server right now. Please ensure it is running and try again." The server is running and the URL works from a browser outside of my network. 

 

@@ebr, I had not followed the process listed as the answer in that thread, but I did per Luke's instructions. It does not work, and will not add to app.emby.media as per above. Again this has been working for weeks without any of the changes I have now made. WHY?

 

buzz

[Luke 42079]

 

 

That is what I mean. The server disappeared from app.emby.media. It was NOT deleted, just disappeared. When I try to add it back on app.emby.media I get "We're unable to connect to the selected server right now. Please ensure it is running and try again." The server is running and the URL works from a browser outside of my network. 

 

Can you provide a copy of the contents of the browser debug console? thanks.

[buzzra 3]

The contents of the debug console is attached.

 

Thanks

 

buzz

 

DebugConsole.txt

[Luke 42079]

Can you attach the emby server log just so that i can rule out any possible issues there?

 

The browser console says that it timed out while trying to connect, but most likely the issue is something else. Notice the CORS error in the second to last line. The most likely source of the problem here is either a browser setting you configured, browser extension you installed, your reverse proxy settings, and/or your reverse proxy not preserving the CORS response headers applied by Emby Server.

[buzzra 3]

Here is the Emby server log. I saw that CORS error and am reading up on it. I don't understand why it doesn't affect a plain web browser.

 

Thanks for the help

 

buzz

 

 

 

embyserver.txt

[Luke 42079]

Because when you put the url in the address bar, it's not cross-origin. When you use app.emby.media, any requests that go outside of app.emby.media are cross-origin and need those headers in order to be allowed.

[buzzra 3]

That makes sense. Did something change to cause this? Is the cross-origin check new? It had been working fine for a while.

 

buzz

[Luke 42079]

CORS security is a browser requirement, not anything coming from Emby. Emby is already doing what it's supposed to be doing in this area. Notice the 401 response error in your browser log - except, there's no matching 401 response in the Emby server log.

 

And further evidence - those same /system/info/public urls that the browser says are failing, your emby server log shows successful responses:

2019-07-27 15:32:29.237 Info HttpServer: HTTP GET XXX/emby/system/info/public. UserAgent: Mozilla/5.0 (X11; U; U; Linux x86_64; en-us) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Puffin/7.7.2.30719AP
2019-07-27 15:32:29.237 Info HttpServer: HTTP Response 200 to XXX. Time: 0ms. XXX/emby/system/info/public

This means the request was successfully processed by Emby Server, and a response was sent, but something in between the server and your browser took that response and changed it to a 401 error code.

 

More than likely it's your reverse proxy, but it could have been a browser extension or browser setting.

[Luke 42079]

I would suggest taking a look at @@pir8radio's nginx configuration and comparing it to yours.

[pir8radio 1312]

Yea the out of the box configs someone is writing for emby/docker/nginx are just bad...    Generally you can tell that is the case because they try to link the main config to generic site configs to make it easier for the end users..     Just write your own config when using nginx...   Click my avitar and use that single file config as your starting point for emby. 

[buzzra 3]

I under stand all of this, but "out of the box" everything just worked for a long time. It would make sense if this was a first time set up, but it is not. It is(was) a WORKING set up. It stopped out of nowhere when the app.emby.media site dropped the server. Since then I cannot use Emby Connect, or add the server manually to the Android TV, Fire TV, or Android app. After all the changes I have made from this thread, I resent an email to the admin account and got the server re-added. Emby Connect worked one time, then the server was gone from the website again. 

 

buzz

[Luke 42079]

I understand the timing seems to coincide with that event, but i can pretty much promise that if we dig deeper it will lead to something else.

[buzzra 3]

O.K.

It is a problem in ALL browsers, and on all android devices,so that points to my reverse proxy that hasn't been updated in months and is configured the same as it has always been. Guess "if it ain't broke don't fix it" doesn't apply here.

 

Thanks anyway.

 

buzz 

[Luke 42079]

Click this link to @@pir8radio's profile. He has his nginx configuration in his profile. A lot of users here have been using it as a reference.