Cloudron Forum

Hello @davejgreen @davejgreen said: Is migration of users and email boxes only possible by using the "looking to restore" button for restoring full Cloudron backups? Yes. @davejgreen said: And is that button only available when you first install Cloudron? Yes. @davejgreen said: We have a second server up and running with a newer version of Ubuntu and Cloudron and were thinking about importing each app individually (after backing it up from the old Cloudron onto a backup site hosted on the new Cloudron), but I'm not sure if there's a way to import the users and email boxes? If not, I guess this approach will not work for us, we'd have to use a third site for a full backup. This is not recommended. The new server should be installed with the exact Cloudron version you are currently using. Otherwise you wont even be able to restore the system backup. @davejgreen said: Do we need to purchase another one for the new Cloudron instance? No. Once migrated simply write a mail to support@cloudron.io and inform us and we will switch the licence to the new server. To minimize downtime use the dry-run backup restore option: https://docs.cloudron.io/backups#dry-run-restore This way, you can restore the whole system, without changing DNS records and can validate each app / step manually. The old server stays up and running, serving all the apps, mail, chat etc. After a review of the migration, when ready to switch permanently, go to Domains view and click Sync DNS.

I have fixed this for the upcoming release

Reworking the installation flow a bit might help.

There is also a Logs dropdown button in the backups view which opens the corresponding log file in the logsviewer, from there the full logs can also be downloaded, avoiding the need to ssh into the server.

@samgreenwood are you following the steps in https://docs.cloudron.io/backups/#move-cloudron-to-another-server ? If you need access to your old server simply change DNS manually to point to the old server or modify your laptop's /etc/hosts . my.domain.com 1.2.3.4 (where 1.2.3.4 is your old server IP)

@tecbox thanks for the update!

@difficult222 I have replied to your ticket.

Hi @joseph . Thanks! Yes, the issue was with the encryption password. I successfully created a new app from the backup. However, one question remains: how can I restore a backup to NocoDB without recreating the app? The original restore (to the existing app) kept failing with the role already exists PostgreSQL error. Could this be related to memory limits? I checked and there seemed to be enough memory available everywhere. For context: my NocoDB has many records plus connections to external databases.

@james need to test backup and restore again to find out... will do.

Hello @brambuijs Is this still an issue?

@ghosted @mdc773 9.0.13 has the fix .

@girish said in Attempted to restore Cloudron 9.0.12, receiving error when loading backup configuration and hitting Restore button: @d19dotca I tried to reproduce this but I couldn't figure where to set this IP allowlist in iDrive e2. Maybe it's only for paying customers since I am on the trial plan ? Hi Girish. This link can help, assuming it isn’t gated to paying customers (I’m not sure if it is or not), but hopefully this provides some instructions for setting up an allowlist. https://www.idrive.com/s3-storage-e2/faq-buckets#ip-allowlisting I suspect you’re right though, that it is sending back a non-XML response to provide a response message that it’s forbidden from accessing it. I understand this use-case may be rare, but I think if there’s a way to improve that error handling, it may help others too because at first glance it’s really not clear where the issue could be coming from.

@dylightful If we can have access to your setup, can you write to me at support@cloudron.io ? Would love to debug and figure out why it's failing . Is this reproducible easily - meaning if you take a backup and restore, it fails?

I have updated https://docs.cloudron.io/backups/#restore-cloudron and https://docs.cloudron.io/guides/download-backups/#backup-file-names . Bit of a hasty edit but time is really right these days!

You can check if the server itself is particularly low on memory by running free -m . Can you give nextcloud much more memory (in the Resources section) ? What is it at currently ?

Hello @jamie.mckenzie @jamie.mckenzie said in Wordpress - Unable to restore from backup: Does the automated backup not include files outside of the data folder? The Cloudron backup only includes the database and files in /app/data/ @jamie.mckenzie said in Wordpress - Unable to restore from backup: It doesn't get to restore the key files like wp-config.php - and these files are missing at the backup location (s3) This is indeed strange. For the WordPress Developer app the file wp-config.php is located in /app/data/public/wp-config.php, so it should be included in the backup. @jamie.mckenzie said in Wordpress - Unable to restore from backup: There is no memory issues as the server has plenty of available memory for restore. That the server itself has enough memory is not the point. The point made was that you might need to increase the apps memory limit. @jamie.mckenzie said in Wordpress - Unable to restore from backup: I have tried clearing down the cached files in the backup storage down to the bare minimum yet it still fails. I would strongly advise against tinkering with anything inside the backup. In Cloudron 9 backup integrity checks are added which will fail if you delete files by hand. @jamie.mckenzie said in Wordpress - Unable to restore from backup: Also is there a way to alter the back configuration so more than 10 files are downloaded concurrently Indeed, should we make this configurable @staff? @jamie.mckenzie Could you please share more details about your S3 provider?

yes @james I have also thought of using that. but manually running it on all mailboxes sounds like a pain I don't want to go through. I guess the current way I envision it is writing a script for imapsync that uses the api of cloudron to get all mailboxes and impersonates the users of the mailboxes to auto run imapsync on them. but then again maybe a block of the port is the way to go, so I don't have to write that script. the whole backup and recover process should be done quite quickly anyways. I am wondering though if this is not something others have gone through as well?

oh that is true, I forgot about Cloudron 7 not being supported/tested on Ubuntu 24. So then yes you have to first install Ubuntu 22, then restore Cloudron, then update Cloudron, then follow the guide at https://docs.cloudron.io/guides/upgrade-ubuntu-24/

Hello @leemuljadi I am happy to hear this worked out as intended. If there is anything we could improve in the documentation please let me know.

@skeats you could attempt it yourself. The app is already broken so what can go wrong. There is no guide for a manual restore since this is something that should not be necessary. But in this case, sadly is. If you are not comfortable doing the following, you can contact support@cloudron.io and link this topic in the request. But you will still need to upload the backup to the cloudron server into a given location from the support. Now to the gist of it. The idea would be to install a new Lampstack app. (What is lampstack? Do you mean the LAMP app? Or is this a custom app? I just assume now you are talking about the LAMP app) Copy the extracted backup to your Cloudron server e.g. /tmp/manual-restore/ In that backup included is the Database as an .sql file and the /app/data/ files. To import the Database you would need to follow either https://docs.cloudron.io/guides/import-mysql/ and then copy all files of /tmp/manual-restore/ app-backup/data/into/home/yellowtent/appsdata/APPID/data/` This would be the "manual" way.