In theory, it is supposed to go away after you reboot.

Right, we don't recommend upgrading since we trying to keep our testing simple. Security updates are enabled for the base packages that we use. We don't really use many base packages - nginx, collectd. Rest are all containerized (mysql/mongo/redis/email etc) and updated via our docker updates. Docker, nodejs itself are all installed from binaries and not via apt.

Thanks for the thorough reply @girish , I've updated my DNS accordingly and the certificates renewed! I'll figure something out with the Github Pages (or self host on Cloudron!)

@nebulon Thank you very much! I had a similar problem, probably also originating in an incomplete schema migration — the error message I got was ER_BAD_FIELD_ERROR: Unknown column 'apps.reverseProxyConfigJson' in 'field list'(putting it here so anyone encountering the same may find it) — anyway, running the command /home/yellowtent/box/setup/start.sh as root just as you suggested fixed the problem at once, even without a reboot.

Nice, thanks @girish

I would also delete ~/.cloudron.json for good measure since we change the format of the config a few times and maybe you have something from an older CLI version.

Good point, I thought this would be triggered by the security update job from ubuntu already, but apparently not.

Is just DKIM and SPF not required or generally that domain not for sending out emails? If the latter is the case, the checks can be disabled by setting the Email Relay to "Disable" in the Outbound tab of the Email settings for this domain.

@smilebasti Possibly because the destination file system does not support hard links. In the Backup -> Configure, there is a checkbox to disable hard links.

Hopefully, this will get automatically fixed in the next release since we removed the unnecessary OAuth sign up flow.

@girish WOrked like a charm, thanks!

@imouthesmp You can just restart the droplet. No need to stop/shutdown apps. All the apps and Cloudron dashboard will start automatically after a reboot. You can also resize the droplet (CPU/Disk/RAM) as you see fit and Cloudron will adapt automatically.

Thanks all! I just installed it on 1 of my Cloudron servers (at DO) to see and experience if and how it works.

@nebulon Solution was 1.) sudo dpkg-reconfigure tzdata => set Timezone to Berlin 2.) sudo hwclock --systohc Now is the Hardwareclock the same as my real clock. Thanks for your help BR Axel

Hi @derek sorry for the delayed answer, did you manage to solve this after the TTLs have expired from your attempts?

@girish obviously it'll depend on the app, but out of interest, what is the ballpark figure for this? e.g. for Loomio?

Is anyone doing this yet? Seriously considering doing it myself!

@girish All these years and it’s still a pain >_< Edit: I’m referring to Linux distros ofc, not Cloudron.

@merox If you want to experiment with installing new packages, I think the best bet is to build your own package. The source code for the nextcloud package is at http://git.cloudron.io/cloudron/nextcloud-app . You can build that package by following the tutorial at https://cloudron.io/documentation/custom-apps/tutorial/ What you would do is to add the additional package you want at https://git.cloudron.io/cloudron/nextcloud-app/blob/master/Dockerfile#L6 . Would that work?