Cloudron Forum

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!

@robi Actually, I'm still on the free version of Filerun. I've been using it for quite awhile. Once they moved to a paid version they removed the free one for download unless you already had it running. So, I'm good.

@jayonrails If you were replying to my concern, I can just see the Forum posts now: "Help, my Ente export isn't working on my library with 12867 images, and 1380 videos! It's supposed to work!"

Good luck and best wishes to whoever uses this, but I'm sticking with whatever lets me leave my media in their existing folders. Back in the day FileRun did this for free, but they now charge 99 EUR. I tried ResourceSpace but it also moves everything around to its own organization.

Let me say that moving ANYTHING from a media cache to another S3 bucket is just an exercise in frustration. Listen, I know modern software promises that everything will work, but it just doesn't sometimes. I also have done this dance with Mastodon, and in the end the ONLY thing that works is me saving my original media which I use on my own instance, locally. When I move the instance, I just refer to a screenshot of what my Mastodon looked like, and use the same image files for logo and icon and etc. Trying to get x number of weeks, or even months, of accessed media to transfer over???? Forget about it. Really. It's just not guaranteed. If you are going to move your instance, download your followers, download your personal media, download your hashtags, moderation list, etc., EVERYTHING, and when you are finished setting up your new instances, reupload everything. Inconvenient? Sure. "But mastodon said it should work!" - but it doesn't. I think the reason I accept it and just work around it is because I am the one still in charge of my media. It is my privilege to download my info, save it, and be able to use it again.

But transferring over a cache?? Why? I tried, too, but as I observed the nature of Mastodon, why would I expect that to even be possible? The toots I like, I save. The links that caught my eye, I followed and saved with my ArchiveBox. The toots go flying by, and in a week there's simply been too many.

Thank you @robi, it was the invisible .htaccess that wasn't getting copied over that was the culprit (even though I cp -R'ed).

@girish Sorry, this is using the LAMP app in order to install Omeka Classic. Some plugins I want to try install only into Omeka Classic. I've looked in the dir which @robi mentioned, tweaked somethings, but still Omeka won't install. My apache conf (with my tweaks in bold

<VirtualHost *:80>
    **RewriteEngine On**
    DocumentRoot /app/data/public

    LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" proxy
    CustomLog "|/bin/cat" proxy
    ErrorLog "|/bin/cat"

    <Directory /app/data/public>
        **Options FollowSymLinks**
        AllowOverride All
        Require all granted
    </Directory>

    # Do not remove this include. It's required for your app to see the Real IP
    Include "/app/code/apache/rpaf.conf"
    # This line can be commented out, if you do no require PHPMyAdmin Access
    Include "/app/code/apache/phpmyadmin.conf"

</VirtualHost>

And my .htaccess in /app/data/public is:

RewriteEngine on

# If you know mod_rewrite is enabled, but you are still getting mod_rewrite
# errors, uncomment the line below and replace "/" with your base directory.
#
RewriteBase /

(based on https://forum.omeka.org/t/help-with-htaccess/1191).

The error message at https://omeka.example.com/install

Omeka
Installation Error
mod_rewrite is not enabled.
Apache's mod_rewrite extension must be enabled for Omeka to work properly. Please enable mod_rewrite and try again.

How do I enable please?

I've scheduled myself to ask for an update 2 months from now.

If @andreasdueren has ko-fi account or something I'll pitch in for coffees!