Solved in support@

@eddowding doesn't completely solve your issue as it's not about installing app, but perhaps Alex should just be an App Operator for specific apps? https://docs.cloudron.io/apps/#operators

Restic: https://restic.net Supported repos out of the box: https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html Other repos when combining restic with rclone: https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html#other-services-via-rclone A starting point: https://docs.cloudron.io/guides/community/restic-rclone/

Porkbun issue is fixed in 8.1

The porkbun issue is fixed in 8.1

@timka thanks for verifying

@joseph ah, there you go. I have indeed updated to 24.04, and presumably it was before this instruction was added. Thank you all for the help, guys, all is well now

Mm, ok thanks, but I think we need more information to debug. Hopefully, it doesn't happen again!

We can not help you. You have your answer. Look for VPSes which unblock port 25. I frequent lowendtalk and lowendbox for this.

Thanks for sharing that and glad it worked out in the end.

Ah this is good information and indeed a likely a problem for rsync backups with a lot of files (not sure how the rate-limit turns out in the end though)

It seems this worked out? Atleast, I see a login screen here. [image: 1731514135008-94c957b3-6fc7-481a-9dd2-96d7c87aa228-image-resized.png]

It looks like the problem is indeed gone with 8.1 Thank you!

Indeed those leftovers should have been purged. Maybe some bug somewhere then. Do you have a way to reproduce this?

Should be fixed now. A new weblate package is also out with probably a fix to the root cause.

8.1 is in unstable now, these issues are fixed there.

@ekevu123 Previously, we used something called "CPU Shares" (--cpu-shares in docker) . This option was a bit hard to understand since it comes to picture only when there is CPU contention between various apps (i.e when a server is overloaded to start with). We removed this and replaced it with an easier to explain "CPU Limit" (--cpu-quota in docker). This corresponds to how many cycles your app should be given. Like, you can say, give only 2 cores max to this app (in any situation). By default, apps have access to all your CPUs. However, isn't the point that the default should be less than that so that one app cannot take down the whole server? We couldn't think of a good default. Otherwise, apps will start out "crippled" and we thought it's better this way. I think if you have apps that are causing problems, only then should you look into tweaking this. This would be a stop gap measure before you try to report the issue and get the app fixed...

Sorry I did say the wrong currency. Thanks that does answer my question. Now I just have to decide if my small home server NUC is worth an extra $200 USD a year.

@jdaviescoates thank you - I've got mail restored using backup, which required a few hours, but the data is there. But I can't really can't see any reason keeping it enabled by default. How many modern mail clients can't handle search across all folders? I understand that you can't satisfy everyone with changes - just wanted to let you know that I'm on the side that is shall not be a default; unless I'm missing something, people lived happily up till 7.5.1

Updates cannot be skipped. This is how all the app packages are tested by us and by (most) upstream projects.