From ceccb9946e2487468135ce673235aa079780a943 Mon Sep 17 00:00:00 2001 From: EuAndreh Date: Sat, 15 Aug 2020 20:07:53 -0300 Subject: Use NGINX to handle the creation of certificates for prosody After a terraform state rm '...' of the server and domain configuration, and recreating the instance again while leaving the dettached one running. I had to do this because I was experimenting too much with the domain and I hit the Let's Encrypt rate limit[0]. Because of that I'll recreate certificates less often so that doesn't happen in the new domain during development of the VPS. I'm not shure if this solution works, but I'll commit just as a checkpoint. I had to change the custom DNS nameservers from Digital Ocean to Vultr and that may take a while, so it's worth having this as a checkpoint in time while I'm off to other things. [0]: https://letsencrypt.org/docs/rate-limits/ --- TODOs.org | 2 ++ 1 file changed, 2 insertions(+) (limited to 'TODOs.org') diff --git a/TODOs.org b/TODOs.org index 5708fe0..8e8bdc7 100644 --- a/TODOs.org +++ b/TODOs.org @@ -158,4 +158,6 @@ This way we test the DNS A record -> Floating IP -> Droplet IP path. We can't do We could use the raw Droplet IP instead of the DNS A record, but I prefer calling it later in order to always test the full DNS resolution. * Questions ** How to best handle IP changes when the server changes? How does this affect the email sending IP reputation? +** Enable 2FA for Nextcloud? +Do XMPP support that too? * Scrath -- cgit v1.3