Cloudron Forum

If you mean the webterminal, then this is into the filesystem of the app, not the host system. Cloudron does not have a webterminal into the host system, as it is not advised to tinker with this. However in this case you should use scp (essentially file transfer via ssh) to put the tarball into the /tmp of the server.

I put storj separately at https://forum.cloudron.io/topic/11670/add-storj-as-backup-option

@privsec said in Can not restore/reinstall cloudron:

I have set up cloudron to use the same 7.5.2 version of my current install.

On the new install after I update the DNS records to the new IP address, I get this

After the cloudron installation, did you do the domain/dns setup and create an admin account? If so, you should not do that.

Setup new server with cloudron --version 7.5.2 Go to https://ip For good meaure, I would power off your old server. This prevents any dns caching issues wrt my.domain.com pointing to your old server. Start restore from the setup view Cloudron will automatically navigate to https://my.domain.com

'Already activated' means that you already setup admin account on that server. After that, you cannot restore anymore for security reasons. For example, if you find a cloudron installation in the wild and try to restore, it won't work. That route is completely locked.

Great! Thank you so much for the detailed and helpful answer 🙏

To follow up, 11GB worked fine too.

image.png

@andreasdueren yes, usually that means the passphrase is wrong.

Should be in next release (8.0), but otherwise you have to apply that one liner manually.

Having to go through a restore, this was baffling with no hints for me too.

I'll make a Feature Request to make this more obvious in the restore dialogue.

The things we learn going through the support requests!

Might not be limited to „lock“ files: Today I had a similar error (first time ever!)

du error: Command failed: du -Dsb "/home/yellowtent/boxdata/mail" du: cannot access '/home/yellowtent/boxdata/mail/vmail/[REDACTED]/mail/dovecot.list.index.log.2': No such file or directory

So is this then fixed by now with getting unbound back alive?

@pbischoff thanks, I have fixed the link.

@nebulon Thank you for your reply. In the instructions it says that first you have to run the command

cd /home/mastodon/live aws s3 sync --acl public-read public/system/ s3://instance-media --endpoint=https://s3.fr-par.scw.cloud

To synchronize local data, cache Mastodon media to the S3 bucket.
I guess that would have to be a different command here on Cloudron.
Now my images load, but the local avatars, server image have disappeared from the instance and the remote images and avatars are not loading. Is it possible that the remote images will load gradually, I don't know.
I've been really struggling with this for a few days now and the result is still not good. 😞

@jdaviescoates said in Backing up multiple Cloudrons to the same backup destination?:

And just to be double clear, having different prefixs results in different paths, right?

yes!

@nebulon you were right.
With the new version 7.3 the restore worked immediately and now baserow is running again.
Thank you for the great support!

@girish Thanks, that works.

@girish perfect! Thank you so much! I really highly appreciate the effort! Thanks! I see it now!

@girish So after the upgrade to 7.2.2 the problem vanished. Closing the Ticket.
Thank you for the help!

@msbt We won't break it intentionally atleast.