Maybe there is some initial startup race in the package. Tbh I am not sure if we can recommend using that, given that we have hit a few issues and there was really not much interest by users, and thus it hasn't really reached a stable package state yet.
For a start is this error easily reproducible when reinstalling?
@girish thanks @nebulon has also pointed out that it's seemingly a bit unstable upstream too:
@nebulon said in Why "rolling release" instead of stable?:
@jdaviescoates given the unstable state of upstream, maybe you can raise issues in their issues tracker on github to iron out those.
@nebulon ah, thanks, I hadn't realised the seemingly unstable state of upstream. But, yeah, it seems a least some of the many issues we have with the Cloudron package aren't only with the Cloudron package.
