Cloudron Forum

@RazielKanos yeah, you will have some down time when migrating. If apps don't change, then you can avoid downtime by restoring using 'dry run' - https://docs.cloudron.io/backups/#dry-run . Once restored on new server, just change the DNS. This way you won't have downtime but with the caveat that you will lose changes that were made to the old server since the backup that was restored on the new server.

@girish said in resolvconf failed by Install to Cloudron:

Did I understand correctly, that cloudron-setup is failing and that the error you posted is from /var/log/cloudron-setup.log ? What's the log lines before the error ? See if you can fix those errors manually and run cloudron-setup --redo .

It's not me this time, but I've hit this before yes cloudron-setup does not work at all on Netcup VPS vServers because they are running some custom minimized version of Ubuntu.

See also this previous thread https://forum.cloudron.io/post/74252

Netcup said on Twitter they would look into it here https://twitter.com/netcup/status/1711394283347960098 but presumably they haven't fixed it.

Always check the CPUs via cat /proc/cpuinfo | grep avx

@girish thanks a lot super fast response. Just installed cloudron this day with the new setup-script. For the people reading this in the future) setting the immutable bit did the trick, no installation like I supposed needed. Works like charme...

@scooke said in Why is netcups DNS so slow?:

Wildcard

I'm using the programmable DNS (CF and Bunny). Maybe that's why it's faster.

All went well, apps are restored and all is running as intended 😄

@Stardenver said in Identify whats causing lags:

So the graph showing 200% is 2 cores on 100% each (or something equal like 4 cores on 50% each)?

The latter is more probable. If you really want to know, run 'htop' from the command line.

This then means, that the system is using cgroups v2 now. I have updated the main docs section at https://docs.cloudron.io/packaging/cheat-sheet/#memory-limit for a start to make an app compatible with cgroup v1 and v2 (I guess in your case its sufficient to only support v2 now.)

@girish & @marcusquinn thanks for the hints!

Finally the AWS guide did the trick, it was a 2 step approach (in my case):

sudo growpart /dev/sda 3

sudo resize2fs /dev/sda3

The netcup image for VPS, Root and Dedicated servers is still there and working. "Latest" would be Ubuntu 20.04 but the image is still based on Ubuntu 18.04 with is fine. The Cloudron version will always be latest because of the auto update on installation. I'm using Netcup and the image on various cloudrons and never had an issue so you should be fine.