I have this problem where Lets Encrypt will not autoupdate properly.
I think the problem might be that I am deploying multiple projects on the same droplet. Every project has its own trellis-instance, site- and trellis-folder are in the same github repo. I think I remember @benword mentioning in an other threat, that this is not the way trellis was meant to be used?
From looking at the cronjob files, I had the idea that maybe every time I provision from a new trellis instance/project, this project will overwrite the cronjob-files and only the cronjobs of the last provisioned project will work, the others will not be triggered anymore.
Am I right with this and what would be a good way to fix this? Maybe have only one trellis-folder in an own github-repo and multiple site-folders in seperate github-repos?
As I’m hosting a lot of very small sites it would be unnecessarily expensive to deploy each on an own droplet, so I would like to avoid that if possible.
My fix at the moment is uptime-monitoring and manually reprovisioning - which obviously is a sh**y solution.