# Make sure to change the same vaules at the Cron Job stage aswell. I’ve created and distributed the installation procedure/command reference over on GitHub as well as below. – SSH Access to the Ubuntu/Debian based machine running UniFi Controller Lastly the automated renewal can be set up as the certificates only stay valid for 3 months. Once converted the certificate can be installed on the UniFi Contoller side of things.
p12 file, this will be done using openssl. pem parts, these can’t be used by the UniFi Controller as is and has to be combined and converted to a. The now approved certificate comes in two. The way we’ll automate this is by using certbot in combination with a cronjob.Ĭertbot will stand up a quick and dirty HTTPS enabled site on the machine to host the Let’s Encrypt request files, once the certificate is approved and downloaded the site will terminate. This is all well and good when applying Let’s Encrypt certificates to websites, but it does get a bit more complicated when combining it with the UniFi Controller, as it doesn’t run a simple website on tcp:443, it runs on tcp:8443. Let’s Encrypt verifies the certificates by looking up the desired hostname with DNS, verifying connectivity with HTTPS tcp:443 and finding the files the request created, read more here.
#Unifi controller linux free#
Luckily this process can be entirely automated and rendered free by using a Linux based controller in combination with Let’s Encrypt. Securing the UniFi Controller web interface with an SSL certificate (HTTPS) is not only important, it’s mandatory in my eyes, especially if the controller is publicly available for use via the app or directly by customers/site owners.
0 kommentar(er)
