HTTPS remote access not working, HTTP working perfectly

[morg1142 0]

First and foremost EMBY is a great product... I have nothing but praise for everyone out there in the development team and those who donate their time to make this an incredible product.  

 

My problem is as followed:  I have various devices from different platforms (iOS, Andriod, Roku3s, Roku Sticks, and even Roku inbedded TVs working perfectly from various remote locations using HTTP remote access.  I wanted to begin to use the HTTPS remote access functionality and I can't for the life of me figure out what I'm doing wrong.  I have the correct ports forwarded in my router (8920 for HTTPS) and I believe I'm setting it up correctly and I'm not getting anywhere.  

 

I was hoping that maybe anyone out there has a step by step guide on how to enable the HTTPS remote access for EMBY.  I've tried to search through various threads but alas no dice. 

 

Any help is greatly appreciated.

 

Thanks in advance,

[Luke 42080]

Currently the self-signed cert we're doing isn't a great solution. It doesn't work well without requiring changes to every single app. You can improve the situation a little by specifying your own trusted cert. Our plan in the near future is to revamp our default cert to use something like LetsEncrypt, which will provide a trusted cert, but I can't say exactly when we'll be getting that done.

[Bart91106 2]

Running 3.0.5854.0

remote access is listed as "HTTP" vs "HTTPS"??

I can't connect to via remote access(Emby Connect) since my setting are for HTTPS.

Also the port for remote acess is listed as "8096" vs "8920".  Was the port changed?

 

 Thanks

[Happy2Play 9782]

Running 3.0.5854.0

remote access is listed as "HTTP" vs "HTTPS"??

I can't connect to via remote access(Emby Connect) since my setting are for HTTPS.

Also the port for remote acess is listed as "8096" vs "8920".  Was the port changed?

 

 Thanks

 

Go to Dashboard-Advanced-Hosting and check "Report https as external address".

Edited January 31, 2016 by Happy2Play

[Luke 42080]

And then after doing see please see post #2 

[Bart91106 2]

Thanks!

I updated the "Report https as external address".

The Emby server remote address now matches remote address in my router, however I'm still not able to connect remotely via the Emby app (android).

It discovers my server, however when I click on it I receive the error "Connection Failure" "We're unable to connect to the selected server..... Please verify..."

I'm at my PC and have the server open.

 

For now it appears this function doesn't work.

[jds828 24]

I'm having the same issues in that https just doesn't want to work.

 

I was thinking of buying a cert but not sure how it works using dynamic DNS. Buying a domain name wouldn't be out of the question either and link that to the DNS.

 

I know that you are looking into a better way of doing the secure connection, would you advise just getting our own anyway? Just an idea but could Emby act as a reseller for certs? That way we might save a bit and you earn a bit.

[carlbme 13]

The best method if using your own cert is to buy your domain name, buy a cert for said domain name, update your dns provider. If you shop around you can get it all for fairly cheap.

 

For example (not sure the policy on stating where things were purchased as I'm not trying to pimp out a site/product so...generic names):

 

I purchased my domain name from "Online Retailer A" for $5/yr

I then purchased a 3 year SSL certificate from "Online Retailer B" for $90 (some serious searching on best deals, plus coupons really saved me big on this one)

I then setup my DNS with "Online Retailer C" for free (they have multiple tiers, since I'm going to be doing less than 100,000 requests per month I fall into the free tier)

I then setup my email relay with "Online Retailer D" for free (again, multiple tiers, only using this for outgoing notifications, no incoming, so...free tier)