Jump to content

IOS app unable to connect to remote server


qkjsdvflmksvclkx
Go to solution Solved by Luke,

Recommended Posts

qkjsdvflmksvclkx

Hi,

 

In the past few days IOS users are unable to connect to my server. When they add the host/port and press connect they immediately get the message "Connection Failure, we are unable to connect to ..."  

 

My server is behind a reverse proxy and has a letsencrypt cert. Any (mobile)browser (including safari on IOS) or Android app can connect without problems.

 

Emby server version: 3.3.1.0 (Running in a iocage freenas jail)

 

Iphone 8: IOS 11.3 Emby App 1.51

Iphone 6S: IOS 11.4 Emby App 1.51

 

I checked the emby server logs but nothing gets added to the log when an IOS client tries to connect.

 

However I noticed in the nginx error log the following string only when an IOS device tries to connect

 

2018/06/14 20:53:14 [error] 8433#0: *8201 open() "/etc/nginx/html/mediabrowser/users/cf6a9ef8632d4c8bbca780e29f6a3691" failed (2: No such file or directory), client: XX.XXX.XX.XX, server: XXXXXXXXXXXXXX.XXXXXXXXXX.org, request: "GET /mediabrowser/users/cf6a9ef8632d4c8bbca780e29f6a3691?format=json HTTP/1.1", host: "XXXXXXXXXXXXXXXXXX.XXXXXXXXXXXXXXX.org"

 

 

Any suggestions?

 

PS: iPad seems to work but I currently don't know what model, ios version and emby app version. I'll update later.

 

EDIT: iPad is on,iOS 10.3.1 and emby app is 1.4.9

Edited by qkjsdvflmksvclkx
Link to comment
Share on other sites

qkjsdvflmksvclkx

Update:

 

The user with the ipad updated to emby 1.5.1 and is now unable to connect! Seems like an issue with the new version of the ios app.

Link to comment
Share on other sites

Sushinor

Hi,

 

I got the exact same issue! I got three ios devices, two of them are on another ios version, however the moment I update emby ios app to the latest version I receive the exact same error on all three devices.

 

Certainly an issue to look into!

Link to comment
Share on other sites

Sushinor

I just tested with 2 out of three devices and I can’t..same scenario I dont even access the server it self. The moment I want to make a connection it says immediately ‘Connection failure’.... without prompting credential screen.

 

No logs are incoming as it can’t even go that far.

Edited by Sushinor
Link to comment
Share on other sites

Can you try it again on your laptop and this time open the Chrome console debugger. Please let me know if the Chrome console shows any errors. Thanks.

Link to comment
Share on other sites

can you do this again, and then click on that red public entry and show a screenshot of that? thanks.

Link to comment
Share on other sites

And what if you put that url directly into the browser?

 

It sounds like you've misconfigured the server address with the online web app

Link to comment
Share on other sites

qkjsdvflmksvclkx

And what if you put that url directly into the browser?

 

It sounds like you've misconfigured the server address with the online web app

 

Resource not found Error 404

The requested resource could not be found but may be available again in the future.

Link to comment
Share on other sites

qkjsdvflmksvclkx

.emby ?

Sorry https://mydomain.org/emby

 

Got a bit to excited and typed to fast :)

 

I tried  https://mydomain.org/emby and no port on android and that works too 

 

So android works with:

iOS/emby.media works with:

 

Any Idea why iOS app is no longer able to handle "Host https://mydomain.org port 443"? Because that definitely worked in version 1.49 (and I think 1.50 too but not to sure on that one ).

 

I think the Android app automatically appends /emby to the url. However iOS app is no longer doing that. I have to check if there is a way to monitor the http calls the android app makes .

 

Edit: i'm currently using BURP suite to setup a proxy and monitor the calls. For android I can see /emby is append. The iOS device is giving me a hard time to work with proxy... Still investigating.

apps.emby.media doesn't append the /emby

Edited by qkjsdvflmksvclkx
Link to comment
Share on other sites

qkjsdvflmksvclkx

My pleasure. Thank you for always responding so fast to any thread on the forum. Excellent support that is much appreciated ;) 

Link to comment
Share on other sites

  • 1 year later...
JordanSL

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

Link to comment
Share on other sites

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

 

Hi, yes removing the port is sometimes a requirement. This isn't necessarily a problem, it's just something that you need to do if that's a requirement for your particular server setup.

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