Jump to content

IOS app unable to connect to remote server


qkjsdvflmksvclkx

Recommended Posts

Glenn
On 7/9/2019 at 4:24 AM, JordanSL said:

Sorry to revive an old topic, but this issue still exists and removing the port was my solution.

 

I'm running emby remotely behind an nginx reverse proxy connecting to its local emby installation.

No 'Emby Connect' account

Connecting via IP https://x.x.x.x/emby port 443 using a self-signed certificate (certificate also requires trusting due to self sign)

Specifying the port results in "Connection Failure" empty port allows connection

 

 

Emby Server version: 4.1.1.0

iOS Emby app version: 1.7.7

iOS version: iPhone 7   12.1.4

Hey @JordanSL how did you set this up?

I'm also running it through nginx and pure safari I can connect to the https:// and see emby, but the emby app no matter what ( with or without port number ) refuses to connect...

Or @Luke any other tips from you?

Link to post
Share on other sites
Luke
18 hours ago, Glenn said:

Hey @JordanSL how did you set this up?

I'm also running it through nginx and pure safari I can connect to the https:// and see emby, but the emby app no matter what ( with or without port number ) refuses to connect...

Or @Luke any other tips from you?

I'm not sure at this point as it appears specific to the connection. Did you update to iOS 14.5?

Link to post
Share on other sites
Glenn
14 hours ago, Luke said:

I'm not sure at this point as it appears specific to the connection. Did you update to iOS 14.5?

Yeah I updated. But seeing on other threads here on the forum, people needed to adjust their nginx Config for it to work.

I’ve tried to do that but without luck so far.

Link to post
Share on other sites
Luke
16 hours ago, Glenn said:

Yeah I updated. But seeing on other threads here on the forum, people needed to adjust their nginx Config for it to work.

I’ve tried to do that but without luck so far.

Ok, let us know if you figure it out. Thanks.

Link to post
Share on other sites
  • 1 month later...
bluesite

i have login problem with emby on ios when the server is running not on Port 8920 (https), i have changed the port to 443 in emby server,

Login from web is working also with emby on android app.

when i try to login from ios over emby app nothing is listed in the logfiles from emby only if i use the standard port 8920

can someone reproduce this problem?

Link to post
Share on other sites
Luke
10 hours ago, helgeb@gmx.de said:

i have login problem with emby on ios when the server is running not on Port 8920 (https), i have changed the port to 443 in emby server,

Login from web is working also with emby on android app.

when i try to login from ios over emby app nothing is listed in the logfiles from emby only if i use the standard port 8920

can someone reproduce this problem?

Hi, try connecting in the Ios app by entering the server address manually.

Link to post
Share on other sites
bluesite

i have tried ths allready, it works only if i use the standard port 8920 but not with other ports,
with the android app it works but not on ios app only on ios with browser.

it seems that the port is fixed in the app or will not take the port that i enter manualy

emby.PNG

Link to post
Share on other sites
Luke

Hi, no, the port is not fixed in the app. What exactly happened?

Link to post
Share on other sites
bluesite

it comes only that login credentials are not right but on my server logs i see nothing when i try to login from ios app, it works with android and windows emby theatre and also from browser. it works also when i try the standard port but i dont want to open to much ports on my router

Link to post
Share on other sites
Luke

If there's nothing in the log file then that means the request isn't even reaching your server.

Link to post
Share on other sites
bluesite

i see this only in my nginx log

x.x.x.x - - [10/Jun/2021:14:03:25 +0200] "OPTIONS /Users/authenticatebyname?X-Emby-Client=Emby%20for%20iOS&X-Emby-Device-Name=xxxx&X-Emby-Device-Id=6EF9A3ED-xxxx-xxxx-xxxx-2FFE53EE6174&X-Emby-Client-Version=2.0.6 HTTP/2.0" 405 241 "http://localhost:12344/" "Mozilla/5.0 (iPhone; CPU iPhone OS 14_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148"
x.x.x.x - - [10/Jun/2021:14:05:57 +0200] "OPTIONS /Users/authenticatebyname?X-Emby-Client=Emby%20for%20iOS&X-Emby-Device-Name=xxxx&X-Emby-Device-Id=6EF9A3ED-D033-xxxx-xxxx-2FFE53EE6174&X

an this here is strange http://localhost:12344/ and confusing me

here is my nginx conf

server {
    listen 443 ssl http2;
    server_name emby.xxxxxxxx.xx;
    proxy_buffering off;        ## Sends data as fast as it can not buffering large chunks.
    ssl on;
    ssl_certificate /etc/letsencrypt/live/xxxxxxxx.xx/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/xxxxxxxx.xx/privkey.pem;
    ssl_dhparam /etc/letsencrypt/live/xxxxxxxx.xx/dhparams_4096.pem;
    ssl_ecdh_curve secp384r1; # Requires nginx >= 1.1.0
    ssl_protocols TLSv1.2;
    ssl_ciphers ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384;
    ssl_prefer_server_ciphers on;
    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload";
    ssl_stapling on;
    ssl_trusted_certificate /etc/letsencrypt/live/xxxxxxxx.xx/fullchain.pem;
    ssl_stapling_verify on;
    ssl_session_timeout 10m;
    ssl_session_cache shared:SSL:10m;
    ssl_session_tickets on;
    ssl_session_ticket_key /etc/nginx/nginx_ticketkey;

    add_header Allow "GET, POST, HEAD, PUT, DELETE" always;
    if ($request_method !~ ^(GET|POST|HEAD|PUT|DELETE)$) {
        return 405;
    }

    access_log /var/log/nginx/access_emby.log;
    error_log /var/log/nginx/error_emby.log warn;

    location /nginx_status {
    stub_status on; access_log off; allow 127.0.0.1; deny all;
    }

    error_page 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 421 422 423 424 425 426 428 429 431 451 500 501 502 503 504 505 506 507 508 510 511 /error.html;

    location = /error.html {
      ssi on;
      internal;
      auth_basic off;
      root /var/www/;
    }


    location / {
        #proxy_pass http://192.168.10.xx:8096;
        proxy_pass https://192.168.10.xx:8920;

        proxy_hide_header X-Powered-By;  ## Hides nginx server version from bad guys.
        proxy_set_header Range $http_range;  ## Allows specific chunks of a file to be requested.
        proxy_set_header If-Range $http_if_range;  ## Allows specific chunks of a file to be requested.
        proxy_set_header X-Real-IP $remote_addr;  ## Passes the real client IP to the backend server.
        #proxy_set_header X-Real-IP $http_CF_Connecting_IP;  ## if you use cloudflare un-comment this line and comment out above line.
        proxy_set_header Host $host;  ## Passes the requested domain name to the backend server.
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;  ## Adds forwarded IP to the list of IPs that were forwarded to the backend server.

     ## ADDITIONAL SECURITY SETTINGS ##
     ## Optional settings to improve security ##
     ## add these after you have completed your testing and ssl setup ##
     ## NOTICE: For the Strict-Transport-Security setting below, I would recommend ramping up to this value ##
     ##         See https://hstspreload.org/ read through the "Deployment Recommendations" section first!   ##
        add_header 'Referrer-Policy' 'origin-when-cross-origin';
        add_header Strict-Transport-Security "max-age=15552000; preload" always;
        add_header X-Frame-Options "SAMEORIGIN" always;
        add_header X-Content-Type-Options "nosniff" always;
        add_header X-XSS-Protection "1; mode=block" always;

     ## WEBSOCKET SETTINGS ## Used to pass two way real time info to and from emby and the client.
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $http_connection;
    }
}

 

Edited by bluesite
update
Link to post
Share on other sites

localhost:12344 is embedded into the iOS app, so that's why you see that as the referrer. You may have to configure your reverse proxy to allow that.

Link to post
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
×
×
  • Create New...