erwyn 0 Posted February 24, 2017 Share Posted February 24, 2017 (edited) Hello there, I'm using Emby on an Amazon Fire stick and I got this problem: -> I have a setup where my Emby server is in the cloud and only secured port is exposed -> I checked in the advance options to report https as my external address -> when I use emby connect -> the ip of the container is used instead of the https address whereas if I go to the dashboard of the server I see that wan address is the https one. -> the unsecured port is broadcasted instead of the secure one hence I cannot connect -> if I manually enter the server -> Everything works fine (even if when I list the servers I still find mine with the wrong address/port) until I shutdown (electrically disconnect) the Fire stick. -> Once restarted, the app seem to use the address and port that were listed on the list of servers interface, hence the wrong ones, and I have to reconfigure everything (plus some caching of the app which forces me to move the port to be able to reconnect correctly). I may be wrong, but it seems that the root of the issue is that either my server does not report the correct address, or let's say the local address instead of the WAN one, or the app is not asking for the good one. And I have to say, of course I can open the unsecured port, but I would prefer the app not to talk through plain http to my server... If I missed anything in the server configuration, please tell me. Edited February 24, 2017 by erwyn Link to comment Share on other sites More sharing options...
Luke 37099 Posted February 24, 2017 Share Posted February 24, 2017 Hi, the correct remote address will be reported to Emby Connect but it will also report the local address as well. is the local address accessible from the device? it tries that first and if it succeeds, then it proceeds with that. Link to comment Share on other sites More sharing options...
erwyn 0 Posted February 24, 2017 Author Share Posted February 24, 2017 (edited) No it's not accessible, it's not even the correct address as it is running in a Docker container. Then I don't get why after restart it is "unable to connect to server". The certificate is a valid one and with a browser I can access the server at this address. Edited February 24, 2017 by erwyn Link to comment Share on other sites More sharing options...
Luke 37099 Posted February 24, 2017 Share Posted February 24, 2017 The certificate is the most likely answer Link to comment Share on other sites More sharing options...
erwyn 0 Posted February 24, 2017 Author Share Posted February 24, 2017 Well it is a valid one (generated via let's encrypt), I checked, and it is working until restart of the fire stick. Browsing with chrome does not trigger any certificate warning. Link to comment Share on other sites More sharing options...
jmc_driven 0 Posted May 20, 2017 Share Posted May 20, 2017 i am having a problem going in to Emby Sent from my SAMSUNG-SM-G930A using Tapatalk Link to comment Share on other sites More sharing options...
mwongjay 64 Posted May 31, 2017 Share Posted May 31, 2017 Hello there, I'm using Emby on an Amazon Fire stick and I got this problem: -> I have a setup where my Emby server is in the cloud and only secured port is exposed -> I checked in the advance options to report https as my external address -> when I use emby connect -> the ip of the container is used instead of the https address whereas if I go to the dashboard of the server I see that wan address is the https one. -> the unsecured port is broadcasted instead of the secure one hence I cannot connect -> if I manually enter the server -> Everything works fine (even if when I list the servers I still find mine with the wrong address/port) until I shutdown (electrically disconnect) the Fire stick. -> Once restarted, the app seem to use the address and port that were listed on the list of servers interface, hence the wrong ones, and I have to reconfigure everything (plus some caching of the app which forces me to move the port to be able to reconnect correctly). I may be wrong, but it seems that the root of the issue is that either my server does not report the correct address, or let's say the local address instead of the WAN one, or the app is not asking for the good one. And I have to say, of course I can open the unsecured port, but I would prefer the app not to talk through plain http to my server... If I missed anything in the server configuration, please tell me. There could be many issues with the way you have it set up. I have a similar set up and here's how it works. 1. I have a DDNS service that resolves my external IP (I use duckdns). So when I have a client I'm connecting to my Emby server the IP I use is <subdomain>.duckdns.org. 2. I have used both of these methods, but you can choose which fits your situation better: 2a. Nginx reverse proxy: My router forwards all external traffic on 443 to Nginx. I have 1 forward set up for Emby that forwards the request to [container IP]:8920. The location is /emby. In this scenario when typing in the IP on a client device DELETE the port number since we've set it in the nginx config 2b. My router forwards all traffic on 8096/8920 to the container IP for Emby. 3. Emby cert location is pointed at whatever directory you have set up to persist the certs generated by LetsEncrypt I don't use Emby Connect. I manually type in the FQDN. 1 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