Jump to content

Cannot login outside of local network


ytzelf
 Share

Go to solution Solved by Luke,

Recommended Posts

Hello everyone,

 

I have this weird bug where I can't login to my emby server from my cellphone / tablet if I'm outside of my home network; login fails with "Request was denied for security." message (cf screenshot below).

Emby website in my browser outside of home network works fine.

 

I am running Emby behind a nginx reverse proxy so I don't connect through emby connect but through an URL like xxx.noip.me:123/emby

App stopped working a few weeks back with no change on the server configurations.

 

 

57b58750506c1_Screenshot_20160818115612.

Edited by ytzelf
Link to comment
Share on other sites

Attached is a log of the mobile app.

Nginx config for emby/ location is below.

 

Had a look at the mobile app logs and there seem to be error related to my subscriber status.. I am however a premium user

 

Might also be of interest that i'm using CM13 latest nightlies on my Oneplus X.

 

 location /emby {
                access_log              /var/log/nginx/emby_access.log;
                error_log               /var/log/nginx/emby_error.log;
                proxy_set_header        Host $host;
                proxy_set_header        X-Forwarded-Proto $remote_addr;
                proxy_set_header        X-Forwarded-Protocol $scheme;
                proxy_set_header        X-Real-IP $remote_addr;
                proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header        Upgrade $http_upgrade;
                proxy_set_header        Connection "upgrade";
                proxy_http_version      1.1;
                proxy_redirect          off;
                proxy_pass              http://127.0.0.1:8096;
}

970a3289-1d1d-42d2-8db4-6f1d1bfc184d.log

Edited by ytzelf
Link to comment
Share on other sites

I'm getting the same error (as posted in http://emby.media/community/index.php?/topic/37782-request-was-denied-for-security-error/), yet I'm not using a reverse proxy and am using Emby Connect.

This is only when I'm outside my network and was working a month or two ago, both on a wifi network and on 4g/LTE.

I can connect if I use a web browser on my mobile device (ie chrome), so I know the remote capability is working. Seems to be only the android app. Possibly changes in the security settings?

Link to comment
Share on other sites

By default I use Emby Connect, but I've tried direct as well entering manual server details.

I've just tried turning off https by unchecking "Report https as external address", and it works!

So is a self-signed certificate issue?

Edited by ACB
Link to comment
Share on other sites

So your issue was trying to run SSL using the Android APP?   Disabled SSL and it works.   Lets see what the OP comes back with and find a pattern...

Link to comment
Share on other sites

  • Solution

Are you able to install apps from the play store? try installing the android system webview app.

  • Like 1
Link to comment
Share on other sites

Yes, I can install from the play store. I've installed the android system webview app, and re-ran Emby and now get a black screen? I'll reboot my phone and try again.

Just rebooted, and still getting a black/blank screen when I run emby now. :-(

Edited by ACB
Link to comment
Share on other sites

Oddly enough it still can't find the webview app so i guess i would just remove it. It's probably not worth looking into whatever variables your modded OS is throwing at it.

Link to comment
Share on other sites

I'm connecting directly (no emby connect).

My OS is CyanogenMod 13 based on Android 6.0.1 but I doubt it's relevant since I get the same error on my gf Shield which is stock OS.

 

I installed the android webview app and now I don't get the popup "Request denied...". The colored circle keeps spinning and I'm brought back to the welcome screen ("Next"... and then "Skip", connect manually etc.)

 

New log attached, thanks everyone for the assistance!

ef53e1e3-6934-4615-a187-7e0d59fb6ded.log

Link to comment
Share on other sites

To all that still can't connect:

 

- If you are trying with HTTP (port 8096), have you followed https://github.com/MediaBrowser/Wiki/wiki/Connectivity tips ?

- If you are trying with HTTPS (port 8920), are you using self-signed cert or custom one? Is it a full chain pfx? Is the pfx imported into client device? Is your issuer trusted?

 

 

Luke, I believe https://github.com/MediaBrowser/Wiki/wiki/Connectivity has to be updated for the particularities of HTTPS 8920 (those quoted above)

Link to comment
Share on other sites

Well I'm not using https in my local network but I am using https for connecting to nginx which then proxy_pass to localhost:8096.

Using a self-signed certificate.

 

Again, it was all working fine until a few month back (can't pinpoint the exact update).

Link to comment
Share on other sites

Well I'm not using https in my local network but I am using https for connecting to nginx which then proxy_pass to localhost:8096.

Using a self-signed certificate.

 

Again, it was all working fine until a few month back (can't pinpoint the exact update).

 

Hmm... that's an unusual setup... I guess.

Do you have knowledge of how the http headers are passed via the reverse proxy? If they are wrong... you may be confusing Emby Server or even Emby Mobile

Link to comment
Share on other sites

Hmm... that's an unusual setup... I guess.

Do you have knowledge of how the http headers are passed via the reverse proxy? If they are wrong... you may be confusing Emby Server or even Emby Mobile

 

 Unusual if running just emby on the machine but since I'm running a whole bunch of other services it does provide a single access point with nice URLs.

 

I am not knowledgeable on the innards of http headers in nginx; but my configuration and which headers I am modifiying with the reverse proxy is there

 location /emby {
                access_log              /var/log/nginx/emby_access.log;
                error_log               /var/log/nginx/emby_error.log;
                proxy_set_header        Host $host;
                proxy_set_header        X-Forwarded-Proto $remote_addr;
                proxy_set_header        X-Forwarded-Protocol $scheme;
                proxy_set_header        X-Real-IP $remote_addr;
                proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header        Upgrade $http_upgrade;
                proxy_set_header        Connection "upgrade";
                proxy_http_version      1.1;
                proxy_redirect          off;
                proxy_pass              http://127.0.0.1:8096;
}
Link to comment
Share on other sites

I don't see anything out of the expected... but I'm not an expert in these headers, too.

Link to comment
Share on other sites

I have the same setup (nginx SSL - Emby no ssl)  but no android to test. Give it a try on my server and report your findings. If it works then we can start looking into your nginx setup.
 

Edited by pir8radio
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...