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.

Hi there, SSH login is usually handled by the the server provider. Cloudron does not have a UI to manage SSH login methods. If you are locked out of your server, usually your VPS provider has a way to reboot the server with a SSH key setup or a reset root password. Otherwise if for some reason this does not help in your situation you can try to enable Cloudron remote support in the support view of your Cloudron dashboard and then send a mail to support@cloudron.io with your domain details. This may allow us to reset your SSH login details. best, Johannes

Usually, "Killed" means it ran out of memory when importing. Can you try to restore again and see "dmesg -w" output in parallel to see if that is indeed the case? You can bump the memory limit for the restore logic as indicate here - https://cloudron.io/documentation/troubleshooting/#backups

Quick update: I just manually ran another system-wide backup and it was successful, so it seems it may have just been a one-off and probably won't happen again anytime soon, was likely just coincidental I was making a bunch of changes to it yesterday considering other system backups proceeded without issue since the time I made those changes. But I'd love to get a second-set of eyes for insight into if this is something I should fix to prevent it in the future or just a one-off type of thing that can safely be ignored.

@girish They are unusual I would say, yes. It's a file that is being updated on a daily basis so it has a file history of 30 different versions in NextCloud. They are .db.crypt12 files, which is a database backup of WhatsApp about 120MB in size.

I think this could be a very interesting feature, eg. to isolate personal apps from other domains and apps... Also, this feature allow to do a good workload plan setting up different VPS. Many thank's a lot!

Merci beaucoup!

For others looking for examples, there's a bunch of custom app templates I made that should help getting started: https://git.cloudron.io/cloudron/tutorial-php-app/ https://git.cloudron.io/cloudron/tutorial-nodejs-app https://git.cloudron.io/cloudron/tutorial-basic https://git.cloudron.io/cloudron/tutorial-redis https://git.cloudron.io/cloudron/tutorial-supervisor-app

Can you check with docker ps -a if that container is in fact there and then restart it with docker restart <containerid>?

@jdaviescoates said in How install wordpress with www?: Quite possible I just didn't wait long enough too I guess... I think that was it. I actually first tried just adding www redirect again to my WordPress at https://uniteddiversity.coop and waited a bit before trying it and it works fine. Sorry, should've been more patient in the first place!

We will fix the pricing page, I agree it's a bit misleading.

@valkalon Cloudron support is still the best

I think there's a genuine case in the future where if we introduce per-app admins, then app admin can access terminal of one app to see traffic (and sniff ldap/db creds) of another app. I think it's an excellent suggestion to remove it!