@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?

@girish You're always so quick! haha Thank you so much!

@girish Your guess is entirely correct. I'll try it out. Edit: Worked. Yay

@nebulon It's a good start!

@nebulon i totally understand your point. i was just unsure because of the statuspage. Thanks for clearing this up !

@girish I second this

Hi @girish , I see, it seems to be that indeed. The server runs on Upcloud actually. I will try one of the solution you propose. Many thanks for your help, d

To know the backup scope, you can sum up all the apps listed there + email data + box data. Then you would have to multiple that by the number of backups which are stored (eg. once every day for 1 week or so) This would be the maximum of storage required using the tarball method. For rsync, it would be much less since it would do incremental backups.

Is there any update on this ?

@girish yep. minio backend

For a start, we have added a UI to set the timezone for the next release.

The emails I retreive through Mozilla Thunderbird. i tried test send/receive emails with gmail, yahoo, outlook, yandex—it works fine. Some info i just got is the sender uses Amazon SES for mail delivery.

Yes that eventlog entry was simply not created, this was fixed actually a few days ago with https://git.cloudron.io/cloudron/box/commit/93199c7f5bb491629c865b283a46ecdaef59741f

Thank you @nebulon The update has not happened it. Shows the same error yet. Will patiently wait however if nothing is needed to be done at this point. Thanks!

Indeed, there was a bug which is now fixed for the next release.

@girish As far as I know, it's correct - unless DKIM has the IP included, since that did change during the migration. Unfortunately, the Email section of Cloudron wasn't properly giving the needed information - previously it was saying DKIM was incorrect, but the display just said something like "expected null to equal null". DKIM isn't showing in the Email status page at all with the workaround I added here. I'll put that in as a separate issue, though, once the update comes out and I see the proper message.

@girish I've never changed backup method no there should not be any remains from that. I did have a directory from april sitting around at 8.6 GB though . Removing that still leaves Other quite large though, so I'll appreciate more hints if you have any.

@d19dotca Indeed, there was a typo in the eventlog code. I have fixed it for the next release - https://git.cloudron.io/cloudron/box/commit/ae5722a7d4865a1924737a7e7d1697c6c9b94d6e

@timmeh Your assessment is correct. If you switched the backups to rsync mode, you can remove the .tar.gz files. They are left overs from your previous backup. Maybe we can add an option to remove the old backup files (of previous configs). But of course, that will require cloudron to remember previous config as well. Also, to be 100% clear, only remove the .tar.gz files. Do not remove any other files in the snapshot directory. The snapshot directory is the "working directory" of the backup system and stores the previous state.