Jump to content

Can not connect to Emby Server from Android TV Box


ACox

Recommended Posts

Can anyone explain why

1. I can connect to my Emby Server on Win 10 pc using my android phone and tablet via WiFi. 

2. I can connect from both my LG TVs to my Emby Server using the LG Emmy app via ethernet connection.

3. I have two android TV boxes which both  will not connect to the Emby Server over the ethernet using either the Emby android mobile app or android TV app. The apps on starting show my sever name but on trying to connect the message is cannot connect at the moment check server is running.. Same issue trying to connect manually and Emby sign in

Do I concluded the Emby android apps are not compatible with Android TV boxes.?

5. If I install Plex server on the Win 10 pc I have no issue connecting on my android TV Boxes, my mobiles and LG TVs so why cannot I connect using Emby android on my Android TV Boxes. Very frustrating does anyone have a solution other than to ditch Emby and use Plex in preference.

Thanks for any guidance or help 

Alec Cox

 

 

 

 

 

Link to comment
Share on other sites

Hi.  It could be a certificate issue, security software blocking the device or a problem with the network detection on your server.  Check to be sure the address shown on the dashboard is correct.

Link to comment
Share on other sites

No issue with IP address on dashboard, and I have carried factory reset on both android boxes and only installed the Emby android app. Can you explain further on what you mean by a certificate issue.

 

Thanks

Alec Cox

 

Link to comment
Share on other sites

On 9/27/2020 at 4:57 PM, ACox said:

Can anyone explain why

1. I can connect to my Emby Server on Win 10 pc using my android phone and tablet via WiFi. 

2. I can connect from both my LG TVs to my Emby Server using the LG Emmy app via ethernet connection.

3. I have two android TV boxes which both  will not connect to the Emby Server over the ethernet using either the Emby android mobile app or android TV app. The apps on starting show my sever name but on trying to connect the message is cannot connect at the moment check server is running.. Same issue trying to connect manually and Emby sign in

Do I concluded the Emby android apps are not compatible with Android TV boxes.?

5. If I install Plex server on the Win 10 pc I have no issue connecting on my android TV Boxes, my mobiles and LG TVs so why cannot I connect using Emby android on my Android TV Boxes. Very frustrating does anyone have a solution other than to ditch Emby and use Plex in preference.

Thanks for any guidance or help 

Alec Cox

Is all of this connecting to the server ONLY from your home network (LAN access)?

On your dashboard you will see the address listed looking something like this:

http://192.168.100.11:8096

That has the IP address of your Emby server.  In my case
192.168.100.11

and the port
8096

So in any app instead of trying to connect by name resolution from your router enter the IP and port numbers in the fields in the apps.
When you setup a new server using the IP and port can you now connect on all apps?

Link to comment
Share on other sites

 The android media app offers 3 options to connect

1. Server name Is : AV and is shown a square icon on selecting AV tries to connect but eventually returns cannot connect at present with the option of trying to wake the server cancel or remove server. Attempting to wake server fails.

2. Use Emby connect enter user name and password returned username or password is invalid. Which makes no sense since I am signed in to the server on the PC with this username and password.

3. Enter manually IP address

192.168.1.65 

and 8096

Returns cannot connect check server is running.

Are you saying the server address should be entered

https://192.168.1.65

The interesting fact is that if I run the Plex android app from the the same TV Box the app automatically finds the server AV and I link the box without issuse using link connect or username and password.

Since both my phone and tablet using the Emby media also connects without issue to my server over WiFi I unplugged the ethernet cable and connected the android box to the router via WiFi. All the ways to connect fail!

 

Totally Confused 

Alec Cox

 

 

 

 

 

Link to comment
Share on other sites

No not saying to enter https:// as that's not going to work on a local network using IPs

Enter the numbers for IP and the port number just as I mentioned above. (obviously your server's IP).

Link to comment
Share on other sites

4 hours ago, ACox said:

192.168.1.65 

Are you positive that is the correct address for your server?

Is your firewall allowing (and not blocking) traffic to the Emby server process?

Link to comment
Share on other sites

  Server IP address is correct and windows fire wall is set correctly for Emby and Plex. The fact that the Emby media app available via LG TV  content store access the server without issue on both my LG TV's and my phone and tablet with Emby android app installed access the server without any issued. Logically it can only be compatibility issue  with the Emby Android  apps and the android TV boxes, and  I have no issues running Plex for android on the Android boxes. So I have decided to make the Plex my main media server and accept defeat with Emby on android TV Boxes.

 

Thanks for your help

 

Alec Cox

Link to comment
Share on other sites

@ACox can you try again? Are you still running into this? If you are, can you try this version on the same device?

Thanks !

Link to comment
Share on other sites

  • 1 month later...

I also have problem using my android box to sign into my account. With Plex, it went thru without any glitch. I think the Emby is not so user friendly.

It keeps on looping during the sign in process - select server to the left and sign in to the right.

Link to comment
Share on other sites

Nickoli02

Hi, I had this same problem. New shield TV pro just set up, installed emby, couldn't log in (on local network). Turns out it looks like the version installed from the Play store is super old? version 1.18.54g or something like that? Sideloaded version 3.1.40 from dropbox above and worked easily.

Link to comment
Share on other sites

9 hours ago, Nickoli02 said:

Hi, I had this same problem. New shield TV pro just set up, installed emby, couldn't log in (on local network). Turns out it looks like the version installed from the Play store is super old? version 1.18.54g or something like that? Sideloaded version 3.1.40 from dropbox above and worked easily.

No, those are two different apps.

Exactly what problem were you having logging in?  Is the address shown on your server dashboard correct?

Link to comment
Share on other sites

Nickoli02

Not sure what you mean by different apps? I installed the Emby client on Shield TV from the Play store, tried to log in, and it didn't work. Sideloaded the version from dropbox above, and it worked fine.

Exact problem: I tried logging in with all three methods (by username, manually specifying server IP, also with the connect thru app-generated PIN, all three failed. Here's a snip of server log showing the authentication failure. (I'm positive the credentials were correct, verified several times logging in from other devices)

2020-12-06 16:23:31.088 Info HttpServer: HTTP POST http://192.168.1.25:8096/emby/Users/AuthenticateByName?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 9; SHIELD Android TV Build/PPR1.180610.011)
2020-12-06 16:23:31.089 Error UserManager: Error authenticating with provider Default
	*** Error Report ***
	Version: 4.2.1.0
	Command line: /usr/local/lib/emby-server/system/EmbyServer.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server -updatepackage emby-server-freebsd_{version}_amd64.txz
	Operating system: Unix 11.2.0.0
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: False
	Mono: 5.10.1.57 (5.10.1.57 Wed Sep 11 19:29:31 UTC 2019)
	Runtime: file:///usr/local/lib/mono/4.5/mscorlib.dll
	Processor count: 8
	Program data path: /var/db/emby-server
	Application directory: /usr/local/lib/emby-server/system
	System.Exception: System.Exception: Invalid username or password
	  at Emby.Server.Implementations.Library.DefaultAuthenticationProvider.Authenticate (System.String username, System.String password, MediaBrowser.Controller.Entities.User resolvedUser) [0x00025] in <450b368eae8f4cb8ab4853f8ffe89952>:0 
	  at Emby.Server.Implementations.Library.UserManager+<AuthenticateWithProvider>d__63.MoveNext () [0x0002c] in <450b368eae8f4cb8ab4853f8ffe89952>:0 
	Source: Emby.Server.Implementations
	TargetSite: System.Threading.Tasks.Task`1[MediaBrowser.Controller.Authentication.ProviderAuthenticationResult] Authenticate(System.String, System.String, MediaBrowser.Controller.Entities.User)
	
2020-12-06 16:23:31.089 Info UserManager: Authentication request for emby has succeeded.
2020-12-06 16:23:31.089 Info SessionManager: Reissuing access token: f8fdda57700949d29b8b9b8886136a62
2020-12-06 16:23:31.090 Error HttpServer: Error processing request
	*** Error Report ***
	Version: 4.2.1.0
	Command line: /usr/local/lib/emby-server/system/EmbyServer.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server -updatepackage emby-server-freebsd_{version}_amd64.txz
	Operating system: Unix 11.2.0.0
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: False
	Mono: 5.10.1.57 (5.10.1.57 Wed Sep 11 19:29:31 UTC 2019)
	Runtime: file:///usr/local/lib/mono/4.5/mscorlib.dll
	Processor count: 8
	Program data path: /var/db/emby-server
	Application directory: /usr/local/lib/emby-server/system
	System.ArgumentNullException: System.ArgumentNullException: Value cannot be null.
	Parameter name: appName
	  at Emby.Server.Implementations.Session.SessionManager.LogSessionActivity (System.String appName, System.String appVersion, System.String deviceId, System.String deviceName, System.String remoteEndPoint, MediaBrowser.Controller.Entities.User user) [0x0000e] in <450b368eae8f4cb8ab4853f8ffe89952>:0 
	  at Emby.Server.Implementations.Session.SessionManager+<AuthenticateNewSessionInternal>d__88.MoveNext () [0x00329] in <450b368eae8f4cb8ab4853f8ffe89952>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <0e06830de9a44394a7e366951eabca52>:0 
	  at MediaBrowser.Api.UserService+<Post>d__14.MoveNext () [0x0010d] in <8725b7dbc02540d7b05eb6d1638ee0aa>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <0e06830de9a44394a7e366951eabca52>:0 
	  at Emby.Server.Implementations.Services.ServiceController+<GetTaskResult>d__12.MoveNext () [0x00081] in <450b368eae8f4cb8ab4853f8ffe89952>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <0e06830de9a44394a7e366951eabca52>:0 
	  at Emby.Server.Implementations.Services.ServiceHandler+<ProcessRequestAsync>d__4.MoveNext () [0x001da] in <450b368eae8f4cb8ab4853f8ffe89952>:0 
	--- End of stack trace from previous location where exception was thrown ---
	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <0e06830de9a44394a7e366951eabca52>:0 
	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <0e06830de9a44394a7e366951eabca52>:0 
	  at Emby.Server.Implementations.HttpServer.HttpListenerHost+<RequestHandler>d__51.MoveNext () [0x00bd3] in <450b368eae8f4cb8ab4853f8ffe89952>:0 
	Source: mscorlib
	TargetSite: Void Throw()
	
2020-12-06 16:23:31.091 Info HttpServer: HTTP Response 400 to 192.168.1.23. Time: 3ms. http://192.168.1.25:8096/emby/Users/AuthenticateByName?format=json

 

Link to comment
Share on other sites

5 hours ago, Nickoli02 said:

Huh, that's weird, the dashboard says Emby server is up to date. Sorry, I didn't look that closely at server side version =/

image.png.4df5f3a0b3d38603fe4915ee0729b022.png

It might be having trouble getting out to the internet to make that determination, but there is a newer version available.

Link to comment
Share on other sites

8 hours ago, Nickoli02 said:

OK I updated to https://github.com/MediaBrowser/Emby.Releases/releases/download/4.6.0.7/emby-server-freebsd11_4.6.0.7_amd64.txz and reinstalled the app from the play store and it's working fine. Whoops!!

And now I'll make a mental note that emby-server needs to be updated manually from time to time :)

Hi.  You have now installed the beta server.  That's okay, but you should be aware that it is not a released version yet.  At this point, do not try to go back to the release until 4.6 is released.

Thanks.

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...