@smilebasti The /home/yellowtent/appsdata is the location of apps. This size seems to roughly match the nextcloud size. As for docker, you should not use du tools inside docker's image directories since they are overlays and the du tool is not smart enough to figure out the size correctly. Try docker system df to get a better idea about the actual size docker uses (this is what is reported in the graph as ~5GB). The volumes also link into appsdata so they might be double counted the du tools. To take a wild guess, maybe you were backing up to the file system for some time before you moved to NAS via SMB? If this was the case, then you should remove the old backups manually from /var/backups. You can just safely nuke all the timestamped directories and the snapshot directory inside it.

@girish Yes, it is, I switched 3. also to every 12 hours + 1 week, and also that one is backing up once a day. I'll ping you.

@girish Could a rule be setup in roundcube / other IMAP client to move inbox emails after a set time? I never really messed around with this idea but I could see it coming in handy for large environments that cannot afford huge data storage.

@Mightymoose There are two flavors of the WordPress app - managed and unmanaged (the former has blue icon and the latter has a grayish icon). Which one did you install? Can you try re-installing the app?

BTW, for the "dot" thing, the mailbox separator in Cloudron is ".". This is why folders with dot don't work. If you create a folder named "foo.bar.baz", it is like subfolder bar under foo and subfolder baz under bar. While using "." as a seperator is not a bug as such, using "/" as a separator instead of "." would have been a better choice for Cloudron but we didn't know this when we started (sadly, "." is the dovecot default too). And also using "/" as separator is required for mailbox sharing to work. We are slowly working towards moving the separator to be "/", step by step.

Indeed, there was a missing normalization. I have fixed it for the next release.

@Nicolas One way to avoid this mistake is use getenv('CLOUDRON_MYSQL_USERNAME'), getenv('CLOUDRON_MYSQL_DATABASE') instead of the raw values. This way when you migrate next time, it will pick up the correct database connection values. The full env list for MySQL is at https://cloudron.io/documentation/custom-apps/addons/#mysql

Yes those log lines indicate a login attempt by an app. Each app makes the requests on the Cloudron local network. So different IPs indicate different apps. In your case it looks like someone/bot tries to login to some or your apps.

OK i have send an E-Mail

@girish said in Using Cloudflare without Global API Key: Can confirm that all zones access is not required in cloudflare anymore. Will update docs. I just added a domain than, just to be more concise we have to specify the Zone Name [image: 1591893338042-af9fe70e-4e52-450f-8527-72561927c428-image-resized.png] unless it will not work with only Zone -> DNS -> Edit permissions at Cloudflare [image: 1591893443438-ab12edf9-baea-4e95-8941-1268a7cb5a96-image-resized.png]

@nebulon about 15-20 every second. When it stops there is a line box:apphealthmonitor app health: 28 alive / 4 dead. Nothing about accessing any sites though.

@scooke said in App or Full backup fails with reference to 'layout'?: If it hangs again should I just email you directly with the logs? Yes!

@Sidias said in App-Timezone: In game I have the wrong time zone Not an expert on minecraft. But it seems that multicraft uses php and you can adjust php.ini to have the correct timezone setting i.e edit /app/data/php.ini and set the data.timezone to one of the values in https://www.php.net/manual/en/timezones.php. If the issue here is bedrock app, it seems we can pass timezone like this https://confluence.atlassian.com/jirakb/set-the-timezone-for-the-java-environment-323392719.html . We can adjust the bedrock app to have the timezone customizable. Is this what you are looking for?

Thank you! A local installation of imapsync on the server did a great and fast job in transfering the emails from one account to the other.

@girish Hi, everything is ok now, after my s3 storage provider fixed their S3 error SSL certificate . Thanks

@d19dotca Just wanted to leave a note that there are some discrepancies in code. I will get it sorted out and give a concrete reply - https://git.cloudron.io/cloudron/box/-/issues/692

@thibaud Are you able to generate credentials for me to test your minio instance? Maybe just create a test bucket for us. Just send them to support@cloudron.io. I just tried to setup backups to a minio installed on Cloudron and that works fine.

If you have a floating IP (in DigitalOcean lingo), elastic IP (AWS) or equivalent, you can make Cloudron use the floating IP (Network -> Interface -> Enter the floating IP). Then you can restore Cloudron to another server, and then when restoring is done, you can switch the floating IP to this new server.

The permission error can be ignored.

@YurkshireLad you should rectify your PTR your email will have a better change of being receive.