Cloudron Forum

Thanks for the prompt response, I got it sorted by creating a new bucket actually.

Hi, if I would like to move Cloudron to another VPS. Is it possible by taking snapshot of current VPS and restore it to the new VPS? Or is it using Cloudron backup instead or the VPS snapshot? Or any recommended way to do it?

and how to restore the backup file?

Thanks all for the response!

Hi, I got this error message while configuring backup storage with Vultr Object Storage:

Does anyone has ever face this before? Thanks in advance.

Thanks all for the response!

@BrutalBirdie is this how to install cloudron with specific version?

wget https://cloudron.io/cloudron-setup
chmod +x cloudron-setup
./cloudron-setup --version x.y.z

and how to check the fresh version installed in the fresh server?
I use Vultr and install Cloudron from the marketplace but when checking with

cloudron --version

it shows

cloudron: command not found

Alright cool thanks guys, I made to install Cloudron on new ubuntu server.

Now based on:
@jdaviescoates https://docs.cloudron.io/backups/#dry-run

I tried several times of this dry-run steps but it will still pointing to the old server IP, any idea why?

and what is gonna happened if I just restore without a dry run?

@james ok thanks I managed get it work using dry-run. so when should I change the DNS record in the domain registrar if using dry-run?

Previously what I have done:

1. set up a fresh Ubuntu 24 server and Cloudron by hand.
2. visit the new IP Address in the browser.
3. I used the backup config from 20 May 25, but then change the backup directory to the latest backup in 26 May 25 (this is the automatic backup, as I cannot open cloudron dashboard already) not using dry-run.
4. removed the local DNS record in the /etc/hosts file of the deleted VPS
5. changed the IP in the DNS record in the domain registrar to the new VPS IP
   Where did I go wrong?

and there is a folder in my storage bucket for backup named snapshot, what is this for? what is the difference with backup?

@james thanks for your help, all good now

@james thanks for your prompt response and sharing the references.

I have go through the documentations that you point out above. It's looking great as Cloudron has already setup a very robust security measure. And yes, it gives much more clarity now!

As per my understanding, the point 1 and 2 is recommended by the documentations and point 3 is pretty much done by Cloudron by internally setting up the IP table in the Cloud Firewall section. If you can confirm my understanding is correct?

I also appreciate for your openness in sharing your thoughts, just in case, I want to clarify regarding more damage and perhaps even create security risks mentioned below?
@james said in VPS Security Hardening:

If you have to ask such a question, you will do more damage and perhaps even create security risks.

Was it pointing to because it's been done by Cloudron as in Cloud Firewall section, so we don't need to mess around with it or do you any other concern?

Thanks for your help.

Hi,

I plan to do security hardening on the VPS that host the Cloudron.

And if below points can affect Cloudron:

1. Disable root login and use sudo user login
2. Change the ssh port
3. Disable all ports except the ssh port with firewall (or any specific port that needs to be open for Cloudron to run? I.e. does http and https need to be open as well?)
4. Kernel hardening

Thanks in advance

Hi,

Why I am getting this not secure indication while pointing the root domain to the wordpress?

Is it related to SSL cert config? and how to fix this?

Thanks in advance

We got this error logs from NextCloud:

1. How can we install the high performance backend from Cloudron?
2. How can we install the missing optional indices from Cloudron?
3. How can we install the Clam AV from Cloudron?
4. Why there is no recording feature in our Nextcloud app and how to activate it?
   

@joseph thanks!

@james local comp time is fine. how do I know it is not correct though?

Btw this issue still persist somehow, but when I tried to open it from incognito mode it's fine, so probably it's the browser cache.

Thanks for the help.