Jump to content

Emby Teather Windows 10 Mobile App can't connect to server


nabikun
Go to solution Solved by nabikun,

Recommended Posts

Hello!

 

Thank you everyone involved to make emby possible.

 

Well, I installed the emby server Version: 3.1.1.0 on my laptop for testing purposes.

Everything went well and I can access my test files over my Xbox One, another PC, and my Lumia 950 XL using app.emby.media on Edge.

 

But I can't connect using the official W10 mobile emby app.

When I try to use "Emby Connect" the app returns the error "HeaderLoginFailure" and "MessageInvalidUser"

And connecting manually to the server returns ""Connection Failure. We're unable to connect to the selected server right now. Please ensure it is running and try again"

 

Using the non official emby app I can connect without problems using the "Emby Connect" and by IP+port.

 

Looking at the server log, the only thing I think maybe is wrong is the GET request the APP is sending to the server:

2016-12-22 20:42:06.4608 Info HttpServer: HTTP GET http://192.168.2.15:8096/emby/System/Logs/Log?name=server-63618013405.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.14986
2016-12-22 20:42:06.5103 Info HttpServer: HTTP Response 200 to 192.168.2.15. Time: 50ms. http://192.168.2.15:8096/emby/System/Logs/Log?name=server-63618013405.txt
2016-12-22 20:42:32.6156 Info HttpServer: HTTP GET http://192.168.2.15:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (Windows Phone 10.0; Android 6.0.1; MSAppHost/3.0; Microsoft; Lumia 950 XL Dual SIM) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Mobile Safari/537.36 Edge/15.14977
2016-12-22 20:42:32.6696 Info HttpServer: HTTP Response 200 to 192.168.2.54. Time: 54ms. http://192.168.2.15:8096/emby/system/info/public

It seems there is a period at the end of the path, after the /public

 

With the period, the browser returns "Unableto find the specified file."

Removing the period the response is correct:

{"LocalAddress":"http://192.168.2.15:8096","WanAddress":"http://189.40.47.25:8096","ServerName":"ED-NOTE","Version":"3.1.1.0","OperatingSystem":"Windows","Id":"6f8f54a8eb1042b0acd59fbddf17a232"}

Any thoughts?

Thank you!

Edited by nabikun
Link to comment
Share on other sites

Hmm, the server is installed on my Notebook running Windows 10.

 

The app is on my Lumia 950 XL.

 

I can access the server using the app.emby.media on the phone (Edge) and using the unofficial app, but not using the official app.

 

BTW, my W10 Mobile is in Brazilian Portuguese, maybe this is relevant.

 

Thank you!

Edited by nabikun
Link to comment
Share on other sites

  • 2 weeks later...
  • Solution
nabikun

Sorry for the late reply.

 

Well, I just received an Emby Theater update on my Lumia 950XL (1.1.51.0), and the problem persist.

But I guess the connection problem is related to the Win10 Mobile version on my 950XL. (Insider 10.0.14977.1000)

I fired up my Lumia 1020 using an old version of Win10 Mobile (10.0.1056.456), installed Emby Theater from the Store and do not have any these connection issues.

 

So apparently there is something happening under the hood with this insider version of Win10 Mobile that is preventing the app working as it should.

 

The weird thing is that everything works (connection wise) using the app.emby.media address on Edge browser mobile.

Thank you!

  • Like 1
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...