![]() ![]() I hope somebody can help with this setup. (when i’m temporary forward port 80 to my HA internal IP, i’m able to get a certificate using the add-on but it’s not working for secure the connection, so also something goes wrong here) So what the best way to secure my HA connection? sudo apt update sudo apt install snapd sudo snap install snap-store. If you don’t have the Snap installed inside your system, first install the Snapd on your machine. I’m already using port 80 and 443 for other things, and don’t want to use duck DNS as i own a domain. Here, we will be using the Snap package manager to install the Certbot tool on our system. (so when i’m connecting to synology over port 5001, the browser shows that the connection is secure) The certificate is renewed by the synology it self.īut i’m running into a issue, with the add-on let’s encrypt it’s common that you also use the duck-dns addon, and forward also the correct ports, 80 and 443 to the HA internal IP. The synology its self is using let encrypt certificate for a secure connect. I have a synology running virtual machine manager, in there i have HA running as a VM. I own a domain name, and have setup the DNS rules there, I like to secure the connection to home assistant using lets encrypt. Save your changes and restart your Plex service. ![]() Custom certificate encryption key: the password you used earlier. Custom certificate location: /volume1/Plex/your domain.pfx. In your Plex Manager goto Settings Server Network. ![]() I’m running Home assistant as a Virtual machine on my synology. Upload the new certificate to the root folder of Plex on your NAS server should be Plex. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |