MRobi 160 Posted May 22, 2018 Share Posted May 22, 2018 (edited) I picked up an Nvidia shield that I'm going to bring down to my camp. I'm trying to get the Emby app and everything configured here before I bring it down. Installed the latest version through Google play store. Launched the app. Went to emby.media/pin and logged in with my pin and received the Pin Confirmed message. Back on the shield it brings me to the "Select a server" page where I can see my server. But when I click on it I get "Server Unavailable The server XXXX cannot be reached. It may no longer be available. Would you like to remove it?" On the server side I'm not seeing it connect. Running 3.4.0.0 I know my network connection is good because it's finding my server name, generating the pin, and I'm able to use other apps such as youtube. I've uninstalled and re-installed. Rebooted. I've manually entered the IP and get the same message. I've logged in using my android phone no problem. Logged in through Chrome no problem. Kodi no problem (using EmbyCon on the same nvidia device). The only issue seems to be the Emby app on the Nvidea. Is there anything I should be trying? Edited May 22, 2018 by IronRobi Link to comment Share on other sites More sharing options...
Luke 37188 Posted May 23, 2018 Share Posted May 23, 2018 Where is your Emby Server located? On a remote network? Have you configured https on your emby server? Link to comment Share on other sites More sharing options...
ebr 14949 Posted May 23, 2018 Share Posted May 23, 2018 Please see: Connectivity Also, update your server to 3.4.1 if available for your platform. Link to comment Share on other sites More sharing options...
MRobi 160 Posted May 23, 2018 Author Share Posted May 23, 2018 Where is your Emby Server located? On a remote network? Have you configured https on your emby server? Local at the moment while I configure the shield and then it will be remote. https on port 8920, but I was trying to connect regularly through 8096. Please see: Connectivity Also, update your server to 3.4.1 if available for your platform. Updating to 3.4.1 seems to have fixed my problem. I made a post in the FreeBSD section on the 17th about manually updating the server as I was updating to what I thought at the time was the latest release. Clearly I missed that 3.4.1 was out. Link to comment Share on other sites More sharing options...
Luke 37188 Posted May 23, 2018 Share Posted May 23, 2018 Thanks for the feedback ! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now