Hello again community. I have SSL running on my truenas box, installed emby and scanned my media, all is fun and working.
Except for wanting to enable https on emby. So I went thru the app setup, selected the HTTPS port for external use and cant login now.
So I disabled HTTP and left HTTPS enabled, didnt work. If I disable HTTPS and enable HTTP and it works but using the IP address and not the FQDN, but thats not what I want.
Suggestions are welcome as always. Appreciate you guys and this forum.
This is one of the weirder quirks associated with Emby. On the one hand, it allows the use of HTTPS, on the other hand, it uses a weird format and does not make implementation easy. I run a bridge here for all my Apps (see @Stux’s youtube video re: same), then I pull a certificate for the IP / FQDN address of choice, the associated CRT and KEY files will be stored in /etc/certificates.
To convert the CRT and KEY file into the format that emby likes, you need to use a OpenSSL command that also removes the need for a password. For my instance, I created a Pool/Apps/Emby directory to store all my Emby stuff in. The weekly command I run via cron (see Settings / Advanced Settings / Cron) is as follows:
If that works as intended (I use root to make this PXF file), start up Emby and log in as a Admin. Use the Network settings in Emby to enable remote access, then select and install the PXF file from inside the /config folder for SSL protection.
Once it’s there, you can save and stop the Emby App. Config the emby App UI to answer on port 443 and then restart the app. It should now offer SSL-protected access.
I chose emby for that reason. I prefer my end points to do the scaling, not the server.
Also, have to love how the UniFi app developer managed to incorporate the TrueNAS certificate with better ease than UniFi does natively. Arguably even easier than using nginx reverse proxy.
Yet other apps like emby and pihole have far more hoops to jump through to get SSL going.
