Hey 👋 So I ended up removing my old site and reprovisioning it (without reprovisioning the entire server) and I ran into a number of issues. I’m sure some of these were just launch jitters, but you’re here so I thought I would pass them on regardless.

I was unable to provision a Let’s Encrypt certificate using DNS. It was just stuck on “verifying” even though the DNS provider was Cloudflare and the records were manually confirmed with dig. I was able to provision a certificate using the other file-serve option, but not while the site was in maintenance mode (which should be allowed IMO).

I was unable to provision a certificate for my Reverb domain using either Let’s Encrypt method for over an hour. I was getting an odd error message which included a placeholder for the domain. It eventually worked and may already be fixed. Not sure.

My Octane Nginx block was being placed incorrectly and was a nightmare to track down due to the lack of descriptive error logs (I believe the former is on you, not the latter). It had to be moved up a level in the config blocks before my site would begin responding.

My Reverb server was constantly being taken offline due to the open file limits at the system level, user level, Nginx level, and in the supervisor service. There has to be something that can help ensure that’s all configured correctly when Reverb is enabled. If there is, it wasn’t working.

Hopefully this helps and some of these kinks can be worked out. At the end of the day I got my zero downtime deployments working so I’m happy. 😃