Cloudron Forum

I suppose it can be marked as solved, but I still run into questions and small issues.

@robi I've been using Servarica since 2020 and have no complaints. I have two of those older Polar Bear servers, and in fact a newer "Black Friday 2024 - UniFied - UniFied FAT" on which I'm running a BTCPayServer due to having 8GB of ram.

So, as long as we don't update the version we have now, for now, we are fine?

Welcome @james! You are part of something special here!

Nah, no thanks. good luck.

Is there no other way to share the logs? I don't feel like downloading an unknown file from a forum.

Since this is all local, sounds like your local MySQL took over the ports of the Cloudron MySQl, and maybe even set some System prefs. If you can edit the standalone MySQL prefs, turn off "start on startup" or similarly worded options. You don't want it starting up first. Then, using what process manager you are familiar with, shut off anything related to MySQL or other DBs, and even Cloudron (as these are all going to be Docker containers anyway). Next, restart the computer. Hopefully you got all the correct prefs, and the only thing with a DB that will start will be Cloudron (you may need to start Docker first, if that isn't set to auto-turn on on startup).

@pangeaner No need I think. It is pretty clear to me and many others. If the wording was changed to remove the idea of "optionally" then users will think they must install them (and how many will then install "ALL" of the n-grams... "pleaase update the docs") and then when they run out of disk space, post something as though Cloudron messed up. You figured it out!; use the process to help you on your self-hosting journey.

Amazing journey. Thank you for documenting it!

@samuk Please always try to show, or explain, what the solution was. This helps anyone else with the same or similar issue.

wowzers!

I eventually figured it out, I suppose. I had activated several login plugins for Facebook, google, X, etc, but hadn't configured them. I just disabled all of them, and now registration works fine.

@japha-3d You realize you are necro-posting, right? My post was FIVE YEARS AGO. Your answer also brought not much more than @murgero response FIVE YEARS AGO. Do not do this.

I thought I set the options, but new users type in the captcha and it just reloads. No message or anything to them. So, they can't register. Any suggestions? Thank you!

it seems a good number of those members are actually homelabbers anyway. I, for one, don't lump self-hosting with homelabs. The issues are too different between the two.

@joseph OP did post on LET - https://lowendtalk.com/discussion/205049/vps-from-prohoster-what-are-the-pitfalls-of-work/p1 and has one response that ought to be decisive.

@daixiwen Even better, they HAVE already allowed for specific backup persistence:

I'm going to go try that out.

The wording definitely makes it sound like at least one backup, "the latest backup", should be available, but my point still stands. As perfect as Cloudron is, I've bumped into hiccups with backups myself, too. And so I pay close attention to them. In the situation you mentioned, you can either let your stopped app backups keep disappearing while you wait for a solution, or you can realize it needs a bit of your help. EDIT: I see you wrote " I'll now try having at least one manual backup set up as persistent and see in two says if it's still there, but ideally this should occur automatically." so good on you for taking it into your own hands. Let us know what happens!

I hear you @daixiwen, but it also makes sense-- "exceed the retention policy", if there is no backup that means the app isn't being used, and so Cloudron, I think, rightly deletes the old backup of an unused app. I think a current attempt to avoid this is to archive an app, but to be honest I don't know what that means - the stopped, archived app IS ALSO the backup?

It is working the way it's intended, I think. You'll find plenty of other posts too where someone stopped an app, let it rest for a long time, and then when they decide to start it up again they discover that it is waaayy behind in Updates. Then they discover it is so far behind updates that they missed breaking changes, and now they can't update but have to start fresh. They blame Cloudron for that. Or, if Cloudron didn't delete a backup, another scenario happens where the user's disk fills up due to all these backups and stopped apps. Again, they blame Cloudron. I know, I know, Cloudron has removed sooo much friction and does pretty much everything perfectly that when something like this pops up, it's a shock, and it's Cloudron's fault.

When I realized this, several iterations ago, I realized that I needed to be more proactive in managing my server and Cloudron. If I stopped an app with the intention of leaving it for a while, I made sure to download the corresponding Backup Configuration, AND the actual backup from wherever it was. I stored them either on my local machine, or another server. This saved me a few times. I also ended up paying for a server with more storage so that I wouldn't accidentally run out of space, and then paid for a 3rd backup destination (either another VPS, or S3, B2, Minio, Scaleway storage, etc.).

Maybe the Cloudron devs can code something that works the way you think it should. Maybe they can't/won't. Is it as simple as some checkbox option that says, "When this box is checked, never delete this backup"? But then they'd have to code that for every app's backup. I am unaware of the complexities of the magic the Cloudron team pulls off. What I do know is ultimately, my data and my machine are under my care, and even though Cloudron makes me an Alita Battle Angel techwise, it's still my responsibility.

@luckow I also have small trimming scissors with which I use to snip those irritating hairs.

Your patience and grit are admirable! As is your beard!