dbarlett 1 Posted August 17, 2017 Posted August 17, 2017 I just recently upgraded my Emby server software to 3.2.27 and the Amazon Fire won't connect to my server from the outside network saying "server unavailable". Before the update everything worked fine with connecting from the outside network with the Amazon Fire. I can connect to the Emby server from my laptop or mobile device outside my network even when the the Amazon Fire will not. Was there an bad update on the Amazon Fire app? I checked all my firewall rules and the ports are working fine. I tried from the Amazon Fire with my Connect account & even a direct entering the server address/port manually and same "server unavailable". On the Emby server dashboard under "Recent Activity" I can see when I connect from the laptop & mobile device and use to see the Amazon Fire log in before the upgrade but since the upgrade I'm not even seeing the Amazon app authenicate.
dbarlett 1 Posted August 17, 2017 Author Posted August 17, 2017 The address I'm going to is https and the cert is a Alpha-SSL purchased site cert till 2020.
Luke 42079 Posted August 17, 2017 Posted August 17, 2017 Can you attach the emby server log? you can learn how to do that here: https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/ Thanks.
dbarlett 1 Posted August 17, 2017 Author Posted August 17, 2017 (edited) Here is log. Edited August 20, 2017 by dbarlett
Luke 42079 Posted August 17, 2017 Posted August 17, 2017 Does your cert require a password, and if so have you entered it into the config page?
dbarlett 1 Posted August 17, 2017 Author Posted August 17, 2017 No it doesn't require a password. When setting up Emby I read some where Emby it didn't work right at the time with passwords on the certs so I have used no password.
Luke 42079 Posted August 17, 2017 Posted August 17, 2017 Ok unfortunately I'm not quite sure. I haven't tested AlphaSSL before. I would probably suggest doing it with a password and entering the password into Emby to see if that changes anything.
dbarlett 1 Posted August 17, 2017 Author Posted August 17, 2017 I'll have to try that. In the new version 3.2.27 did something change in the cert setup? Before the server upgrade and FireTv app getting the update from the Amazon store my exact setup was working just as is.
Luke 42079 Posted August 17, 2017 Posted August 17, 2017 Nothing changed but it's possible the mono runtime version was upgraded for you, and that always seems to have some impact. Luckily we are in process of dropping mono in favor of the newer and smaller microsoft runtime: https://emby.media/community/index.php?/topic/50012-emby-server-for-net-core/ That's not ready for release yet, but this is probably the last time mono will be updated on your distro.
dbarlett 1 Posted August 17, 2017 Author Posted August 17, 2017 That cert with password didn't work after I created the pfx file with a password. Works ok on my phone & laptop from outside my network but still no go on the Amazon. Would doing a fresh install using a backup file from before the upgrade work getting me back up on the Amazon? If so, what version of Emby should I use, 3.2.26 till this upgrade you mention is available for release?
Luke 42079 Posted August 17, 2017 Posted August 17, 2017 I doubt it and I can't imagine that rolling back Emby will change anything. To be honest if I had to guess perhaps the Amazon fire was connected over http previously and you just didn't realize it.
dbarlett 1 Posted August 18, 2017 Author Posted August 18, 2017 @@ebr So what changed in the Amazon app in version 1.4.36a that would cause me to lose connectivity back to the Emby server from the outside network? It only happened when the Fire TV app got updated with this new release. I've totally disabled all SSL on the Emby server turning on only http, changed the ports on my Emby server and firewall, cleared the Emby connect account/save before reconnecting in the Emby connect account, cleared the cache & data from the Emby FireTv app, tried connecting from the outside on FireTv app both from the Connect account and using a direct input and still "server unavailable". This doesn't not happen on my laptop (W10, MAC) or phone (IOS) via the app from an outside network. Of course the app works on the inside of network but that doesn't help me when I travel and why I want to get this remote thing working again.
ebr 16184 Posted August 18, 2017 Posted August 18, 2017 I cannot think of anything in the app that would have affected this. On the login screen, is there a "Send Logs" button?
dbarlett 1 Posted August 18, 2017 Author Posted August 18, 2017 No send logs button. Here is an update since the post. I created a Windows Emby server with the current version on Emby 3.2.27. Connected the server to my Emby Connect account using https with my cert just like I have on the MAC Emby server. I can log into that Windows Emby server and if I go back to switch server I can then access the MAC Emby server with no issues. Both MAC & Windows Emby server at setup the exact same settings. Seems the FireTv app doesn't like to authenticate against the MAC Emby server but has no problems with the Windows Emby server in hitting it 1st.
Solution dbarlett 1 Posted August 20, 2017 Author Solution Posted August 20, 2017 After a factory reset of the FireTv I was able to connect to the Emby server on my MAC. Issue resolved. 1
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