smidley 22 Posted February 20, 2020 Posted February 20, 2020 I have a remotely hosted emby server (outside my house). I am able to connect to the webUI just fine (https://dnsnameofserver.com:8920). However, when I try to connect via the Emby app on my nvidia shield TV, it says the server is unavailable. I don't know what could be going on here since I've set it up a number of times before without issues. When I'm configuring the app, I put in https://dnsnameofserver.com and for the port I put 8920. Any ideas on where I can check to see what's going on?
ebr 16184 Posted February 20, 2020 Posted February 20, 2020 What kind of certificate do you have? Most likely, it is not trusted by the Shield.
smidley 22 Posted February 20, 2020 Author Posted February 20, 2020 What kind of certificate do you have? Most likely, it is not trusted by the Shield. Using a PFX certificate generated by LetsEncrypt.
Luke 42078 Posted February 24, 2020 Posted February 24, 2020 Hi, is the certificate associated with the domain name?
smidley 22 Posted February 25, 2020 Author Posted February 25, 2020 Hi, is the certificate associated with the domain name? Yes it is.
Luke 42078 Posted February 25, 2020 Posted February 25, 2020 Most likely the device is not trusting your certificate. In our mobile app we have ways to allow you to override this, but this isn't something we've added to the TV app just yet.
smidley 22 Posted February 25, 2020 Author Posted February 25, 2020 Most likely the device is not trusting your certificate. In our mobile app we have ways to allow you to override this, but this isn't something we've added to the TV app just yet. Interesting, is there some other more reliable way that I should be getting a certificate?
mastrmind11 722 Posted February 25, 2020 Posted February 25, 2020 Interesting, is there some other more reliable way that I should be getting a certificate? Cloudflare.
ebr 16184 Posted February 25, 2020 Posted February 25, 2020 Before changing your cert setup, you may want to verify our hypothesis by opening up plain http access for your server temporarily and seeing if you can connect that way.
KMBanana 116 Posted February 25, 2020 Posted February 25, 2020 Does the Dashboard show "Remote (WAN) access" as "https://dnsnameofserver.com:8920"exactly?
smidley 22 Posted March 4, 2020 Author Posted March 4, 2020 Does the Dashboard show "Remote (WAN) access" as "https://dnsnameofserver.com:8920"exactly? Yes it does.
Luke 42078 Posted March 4, 2020 Posted March 4, 2020 For now you'll need a trusted certificate. Our Android mobile app has a special override for this situation for self signed certs but we haven't gotten it into the tv app yet.
smidley 22 Posted March 10, 2020 Author Posted March 10, 2020 Before changing your cert setup, you may want to verify our hypothesis by opening up plain http access for your server temporarily and seeing if you can connect that way. I am able to connect via the AndroidTV app using HTTP.
smidley 22 Posted March 10, 2020 Author Posted March 10, 2020 For now you'll need a trusted certificate. Our Android mobile app has a special override for this situation for self signed certs but we haven't gotten it into the tv app yet. I have a trusted cert created with LetsEncrypt. I am able to connect via HTTP, but not HTTPS on the AndroidTV app.
Luke 42078 Posted March 11, 2020 Posted March 11, 2020 You have a certificate but out of the box it is not trusted by the device by default. That's why the app can't connect with it. We need to add a mechanism into the app to allow you to override this, we just haven't gotten there yet.
ebr 16184 Posted March 11, 2020 Posted March 11, 2020 Make sure that your server/network setup is providing the full chain for the cert and I think it should work...
smidley 22 Posted March 11, 2020 Author Posted March 11, 2020 You have a certificate but out of the box it is not trusted by the device by default. That's why the app can't connect with it. We need to add a mechanism into the app to allow you to override this, we just haven't gotten there yet. This type of certificate (letsencrypt) was working for me previously, but isn't anymore.
smidley 22 Posted March 11, 2020 Author Posted March 11, 2020 Make sure that your server/network setup is providing the full chain for the cert and I think it should work... Is there guidance somewhere on how to check this?
Luke 42078 Posted March 11, 2020 Posted March 11, 2020 That could be due to changes on the device. Again we rely entirely on device support for certificates and if you follow the news they are changing their roles on a seemingly daily basis. I would check what ebr suggested.
ebr 16184 Posted March 11, 2020 Posted March 11, 2020 Try this thread: https://emby.media/community/index.php?/topic/46647-firetv-stick-cannot-login-using-https/?p=444648
smidley 22 Posted March 11, 2020 Author Posted March 11, 2020 Try this thread: https://emby.media/community/index.php?/topic/46647-firetv-stick-cannot-login-using-https/?p=444648 I looked over that thread as well, but it’s for Linux, and my server is windows.
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