Letsencrypt on Margrop Blog https://blog.margrop.net/en/tag/letsencrypt/ Recent content in Letsencrypt on Margrop Blog Hugo -- gohugo.io en-US Wed, 17 Feb 2021 20:20:06 +0800 Deploy Your Own Bitwarden Password Management Server https://blog.margrop.net/en/post/deploy-open-source-password-manager-bitwarden/ Wed, 17 Feb 2021 20:20:06 +0800 https://blog.margrop.net/en/post/deploy-open-source-password-manager-bitwarden/ <p>Many people are not comfortable storing their passwords online with services like LastPass. Even though the official claim is that passwords are encrypted and the server cannot see user passwords, some still feel uneasy. In that case, you can deploy the open-source Bitwarden to set up your own password management server.</p> <blockquote> <p>Prerequisites: A VPS server and a domain name with the IP address already resolved to the server.</p> </blockquote> Let's Encrypt automatically synchronizes Proxmox VE and DSM certificates after automatic renewal https://blog.margrop.net/en/post/lets-encrypt-sync-https-cert-to-pve-and-dsm/ Tue, 02 Feb 2021 19:19:38 +0800 https://blog.margrop.net/en/post/lets-encrypt-sync-https-cert-to-pve-and-dsm/ Last time we talked about Let&rsquo;s Encrypt通过DNS TXT记录来验证域名有效性, and the last part of the article was about how to use certbot renew for automatic renewal. Then the automatic renewal is successful, how to synchronize it to PVE and DSM? Below we use a script to perform automatic synchronization. Need to configure SSH password-free login on Proxmox VE and DSM servers Automatically synchronize Proxmox VE certificate Proxmox VE synchronized to this machine Proxmox VE synchronized to LAN cp /etc/letsencrypt/live/blog. Let's Encrypt verifies domain name validity through DNS TXT records https://blog.margrop.net/en/post/lets-encrypt-use-dns-txt-acme-challenge-domain-available/ Tue, 19 Jan 2021 10:39:58 +0800 https://blog.margrop.net/en/post/lets-encrypt-use-dns-txt-acme-challenge-domain-available/ When we use letsencrypt to obtain the free HTTPS certificate, letsencrypt needs to verify the domain name. By default it authenticates like this: The certbot program places a file in the root directory of the web directory. The server of letsencrypt accesses this file through the domain name to verify that the domain name you applied for belongs to you. But sometimes we want to set HTTPS for a certain host on the intranet.