Jump to content

Emby Connect


dravokivich
Go to solution Solved by Luke,

Recommended Posts

dravokivich

Hi All,

 

I posted this thread a little earlier and Luke suggested looking at the issue from an Andorid App point of view.

 

I've setup Emby Connect and my account is linked to my Emby Server account. However on both the web app here and the android app, even though my server is listed to select, it doesn't seem to connect and allow me to access the media.

 

I'm looking for advice more so on possible things to trouble shoot with my hosting setup, more so than from the Andorid app. At present, I'm not by the server so cannot provide those logs.

 

Below are the logs from the latest connection attempt from my Android device. I attempted to attach them as a .log and a .txt but kept failing. I thought the code tags would wrap'em into a smaller box.

15:37:35.123 [main] INFO  App - Response received from: https://connect.mediabrowser.tv/service/servers?userId=4804

15:37:35.874 [Thread-43908] DEBUG App - Server discovery timed out waiting for response.

15:37:35.876 [Thread-43908] DEBUG App - Found 0 servers

15:37:35.931 [main] DEBUG App - Updating header buttons for server selection

15:37:35.936 [main] DEBUG App - Creating server list

15:37:35.936 [main] DEBUG App - 1 servers to display

15:39:49.012 [main] DEBUG App - Switching to MbConnect login activity

15:40:31.741 [main] DEBUG App - Adding request to queue: https://connect.mediabrowser.tv/service/user/authenticate
15:40:32.695 [main] INFO  App - Response received from: https://connect.mediabrowser.tv/service/user/authenticate

15:40:32.971 [Thread-43909] DEBUG App - Entering initial connection workflow
15:40:32.972 [Thread-43909] DEBUG App - Testing local device network connection

15:40:32.975 [Thread-43909] DEBUG App - Android device is connected to a network

15:40:32.976 [Thread-43909] DEBUG App - Getting saved servers via credential provider

15:40:33.006 [Thread-43909] DEBUG App - Scanning network for local servers

15:40:33.009 [Thread-43909] DEBUG App - Getting server list from Connect

15:40:33.010 [Thread-43909] DEBUG App - Getting connect servers

15:40:33.011 [Thread-43909] DEBUG App - Adding request to queue: https://connect.mediabrowser.tv/service/servers?userId=4804
15:40:33.013 [Thread-43910] DEBUG App - mediabrowser.apiinteraction.discovery.ServerLocator>>> Request packet sent to: 255.255.255.255 (DEFAULT)

15:40:33.036 [Thread-43910] DEBUG App - mediabrowser.apiinteraction.discovery.ServerLocator>>> Request packet sent to: 10.20.7.255; Interface: wlan0

15:40:33.060 [Thread-43910] DEBUG App - mediabrowser.apiinteraction.discovery.ServerLocator>>> Done looping over all network interfaces. Now waiting for a reply!

15:40:33.333 [main] INFO  App - Response received from: https://connect.mediabrowser.tv/service/servers?userId=4804

15:40:34.054 [Thread-43910] DEBUG App - Server discovery timed out waiting for response.

15:40:34.056 [Thread-43910] DEBUG App - Found 0 servers

15:40:34.113 [Thread-43910] DEBUG App - Looping through server list

15:40:34.114 [Thread-43910] DEBUG App - Testing local device network connection

15:40:34.116 [Thread-43910] DEBUG App - Android device is connected to a network

15:40:34.117 [Thread-43910] DEBUG App - Adding request to queue: http://192.168.192.27:8096/mediabrowser/system/info/public?format=json

15:40:34.120 [Thread-43911] DEBUG App - Waking server: DUHMEDIA, Id: 400a2cbb1d1c4d32b5c6b2bd9da7b063

15:40:34.121 [Thread-43911] DEBUG App - Sending WakeOnLan over broadcast address. Mac: 28-92-4A-38-3A-19, Port: 9
15:40:39.156 [main] ERROR App - VolleyError com.android.volley.TimeoutError: null
com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:146)
com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112)
15:40:44.117 [main] DEBUG App - Adding request to queue: http://192.168.192.27:8096/mediabrowser/system/info/public?format=json
15:40:49.157 [main] ERROR App - VolleyError com.android.volley.TimeoutError: null
com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:146)
com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112)
15:40:49.161 [main] DEBUG App - Adding request to queue: http://176.61.1.6:8096/mediabrowser/system/info/public?format=json
15:41:04.250 [main] ERROR App - VolleyError com.android.volley.TimeoutError: null
com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:146)
com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112)
15:41:04.255 [main] DEBUG App - No server available
15:41:04.258 [main] INFO  App - **** SERVER SELECTION ****

15:41:04.261 [main] DEBUG App - Testing local device network connection

15:41:04.266 [main] DEBUG App - Android device is connected to a network

15:41:04.268 [main] DEBUG App - Getting saved servers via credential provider

15:41:04.317 [main] DEBUG App - Scanning network for local servers

15:41:04.318 [main] DEBUG App - Getting server list from Connect

15:41:04.319 [main] DEBUG App - Getting connect servers

15:41:04.320 [main] DEBUG App - Adding request to queue: https://connect.mediabrowser.tv/service/servers?userId=4804

15:41:04.324 [Thread-43912] DEBUG App - mediabrowser.apiinteraction.discovery.ServerLocator>>> Request packet sent to: 255.255.255.255 (DEFAULT)

15:41:04.342 [Thread-43912] DEBUG App - mediabrowser.apiinteraction.discovery.ServerLocator>>> Request packet sent to: 10.20.7.255; Interface: wlan0

15:41:04.349 [Thread-43912] DEBUG App - mediabrowser.apiinteraction.discovery.ServerLocator>>> Done looping over all network interfaces. Now waiting for a reply!

15:41:04.641 [main] INFO  App - Response received from: https://connect.mediabrowser.tv/service/servers?userId=4804

15:41:05.353 [Thread-43912] DEBUG App - Server discovery timed out waiting for response.

15:41:05.356 [Thread-43912] DEBUG App - Found 0 servers

15:41:05.440 [main] DEBUG App - Updating header buttons for server selection

15:41:05.442 [main] DEBUG App - Creating server list

15:41:05.444 [main] DEBUG App - 1 servers to display

15:41:09.835 [main] DEBUG App - Server at position 0 clicked

15:41:09.839 [main] DEBUG App - Passing server to ConnectionManager

15:41:09.844 [main] DEBUG App - Testing local device network connection

15:41:09.849 [main] DEBUG App - Android device is connected to a network

15:41:09.853 [main] DEBUG App - Adding request to queue: http://192.168.192.27:8096/mediabrowser/system/info/public?format=json

15:41:09.865 [Thread-43913] DEBUG App - Waking server: DUHMEDIA, Id: 400a2cbb1d1c4d32b5c6b2bd9da7b063

15:41:09.877 [Thread-43913] DEBUG App - Sending WakeOnLan over broadcast address. Mac: 28-92-4A-38-3A-19, Port: 9

15:41:14.966 [main] ERROR App - VolleyError com.android.volley.TimeoutError: null
com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:146)
com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112)
15:41:19.853 [main] DEBUG App - Adding request to queue: http://192.168.192.27:8096/mediabrowser/system/info/public?format=json

15:41:24.917 [main] ERROR App - VolleyError com.android.volley.TimeoutError: null
com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:146)
com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112)
15:41:24.925 [main] DEBUG App - Adding request to queue: http://176.61.1.6:8096/mediabrowser/system/info/public?format=json

15:41:40.013 [main] ERROR App - VolleyError com.android.volley.TimeoutError: null
com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:146)
com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112)
15:41:40.014 [main] DEBUG App - No server available

15:41:40.015 [main] INFO  App - **** UNAVAILABLE ***

*also as I mentioned in the other thread. I'm abe to access Plex remotely without anything extra done. So it's more so from an Emby perspective.

Link to comment
Share on other sites

  • Solution

you may want to check your router's port forwarding with port 8096. we attempt to do it automatically but it doesnt' work for all router models.

  • Like 1
Link to comment
Share on other sites

dravokivich

Cheers Luke.

 

I've gone through a guide for that on http://portforward.com/ already. Although for some reason, My router doesn't seem to list forwarded ports. Although there was no error afterwards.

 

I'll check it out again.

Link to comment
Share on other sites

dravokivich

Hi,

 

Just getting back to close out the thread. Turns out my Router kept having issues saving the 8096 port setting mentioned by Luke above. Eventually got it to stick.

 

Cheers

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