Cloudron Forum

@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!

@marcusquinn I agree with you. But since Cloudron, which works normally on many other servers, isn't on whichever you're using, why keep banging your head against a wall? Move to a server which works. In this regard you have the advantage that moving an entire Cloudron to a new server is straightforward.

OK, since I like doing this kind of stuff, I installed Formbricks just to see where it might be going wrong. I am using a Minio install using runtipi on another server, made a special bucket and user for this test, plugged that info into the /app/date/env file (including REGION), BUT I also added

# Enable for S3-compatible storage that requires path style
# 0 for disabled, 1 for enabled
S3_FORCE_PATH_STYLE=1

I don't know why or how or what, but there is/was some issue in the Minio/S3 world where an update made all future bucket paths virtual_path_style, or maybe it was the other way around? Anyway, I find I need to include this so that my buckets are https://s3.example.com/bucket, rather than https://bucket.s3.example.com.

I then uploaded an image for a background in a survey, and it did, and it saved, and I can see it in the bucket. SO, it is working. Good luck!

I am Canadian, and I bought a macbook pro in switzerland, with swiss keys, but improperly laid out, so it's a constant battle to type correctly - I use stickers, and of course the proper US keyboard.

Two examples I've looked at use the S3_REGION parameter, and my personal experience is that it IS required.
https://formbricks.com/docs/self-hosting/setup/cluster-setup#s3-configuration
https://github.com/formbricks/formbricks/blob/main/.env.example

Do any of the other parameters you've set work and its just the S3 deets that aren't working, or is it the entire env/.env file that isn't being read?

don't give up!

@avatar1024 said in Need AAAA records for ip6 server address for email deliverability:

to make Cloudron as neat with IPv6 as it is with IPv4

The entire internet is still coming to terms with IPv6, still! Personally, at this point, I think it's equally on users to choose VPS providers who offer/don't offer IPv6 as it is on companies like Cloudron. The issues equally stem from software not handling networking competently as it is servers not implementing IPv6 competently. Perhaps we need to share which VPSes are working without a hitch, and which aren't. For example, I was looking into Infomaniak a little while ago because they had a free 1TB storage offer on lowendbox, but I was too late, and now it seems there are hassles anyway with Infomaniak. I've had some servers in the past with network headaches... I just moved away from them.

Due diligence is as easy as checking out https://www.cloudron.io/pricing.html. Most services online make it that easy. The ones that don't, I just skip.

By the way, by leaving Cloudron that must mean you've opted to use something else. I am curious what you've found, or had, that makes it worth not using Cloudron.

Well, the error logs don't contain anything that I recognize as memory related. I have one of those SSDNodes servers which people either love or disbelieve:
Platform Version v8.3.1 (Ubuntu 22.04.3 LTS)
Vendor Red Hat
Product KVM
CPU 12 Core "Intel(R) Xeon(R) Silver 4216 CPU @ 2.10GHz"
Memory 50.51 GB RAM & 4.29 GB Swap
Uptime 5 days

I suppose it needed just that little extra ram past 256MB in order to use the db to make the admin user. Once I upped the ram this is what followed in the logs:

2025-04-08T07:44:57Z 
2025-04-08T07:44:57Z 
2025-04-08T07:44:57Z 
2025-04-08T07:44:57Z 
2025-04-08T07:44:57Z 
2025-04-08T07:44:57Z 
2025-04-08T07:44:57Z                                                                                 
2025-04-08T07:44:57Z                                                                                 
2025-04-08T07:44:57Z                                                                                 
2025-04-08T07:44:57Z                                                                                 
2025-04-08T07:44:57Z                                                                                 
2025-04-08T07:44:57Z                                                                                 
2025-04-08T07:44:57Z  [OK] Cache for the "prod" environment (debug=false) was successfully cleared.  
2025-04-08T07:44:57Z  [OK] Cache for the "prod" environment (debug=false) was successfully warmed.   
2025-04-08T07:44:57Z  [OK] Successfully installed Kimai version 2.32.0 🎉                            
2025-04-08T07:44:57Z  // Warming up the cache for the prod environment with debug false
2025-04-08T07:44:57Z ==> Create admin account
2025-04-08T07:44:57Z => Ensure admin account
2025-04-08T07:44:57Z mysql: [Warning] Using a password on the command line interface can be insecure.
2025-04-08T07:44:59Z 
2025-04-08T07:44:59Z 
2025-04-08T07:44:59Z                                                                                 
2025-04-08T07:44:59Z                                                                                 
2025-04-08T07:44:59Z  [OK] Success! Created user: admin                                              
2025-04-08T07:44:59Z => Starting apache
2025-04-08T07:44:59Z => Tailing app logs
2025-04-08T07:44:59Z [Tue Apr 08 07:44:59.550824 2025] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.58 (Ubuntu) mod_perl/2.0.13 Perl/v5.38.2 configured -- resuming normal operations
2025-04-08T07:44:59Z [Tue Apr 08 07:44:59.550941 2025] [core:notice] [pid 1] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
2025-04-08T07:44:59Z tail: cannot open '/run/kimai/log/prod.log' for reading: No such file or directory
2025-04-08T07:45:01Z - - - [08/Apr/2025:07:45:00 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:45:10Z - - - [08/Apr/2025:07:45:10 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:45:20Z - - - [08/Apr/2025:07:45:20 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:45:30Z - - - [08/Apr/2025:07:45:30 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:45:40Z - - - [08/Apr/2025:07:45:40 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:45:50Z - - - [08/Apr/2025:07:45:50 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:46:00Z - - - [08/Apr/2025:07:46:00 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:46:10Z - - - [08/Apr/2025:07:46:10 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:46:20Z - - - [08/Apr/2025:07:46:20 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:46:30Z - - - [08/Apr/2025:07:46:30 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:46:40Z - - - [08/Apr/2025:07:46:40 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)"
2025-04-08T07:46:46Z 124.122.43.134 - - [08/Apr/2025:07:46:46 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36"

Previously it would reach "clearing the cache", but then crash before "warming the cache". I don't know what any of that means, but upping the allocatted ram to 1GG from 256MB seemed to do the trick.

Looks like there was a CPU surge from Kimai:

Welp, once again, I post a problem that I end up solving, if I had only thought more. Somewhere I read that there might not be enough ram allotted. I checked and the default for this app is 256MB. So I upped it to 1GB, started it, and it finished installing (had to make an admin user), and is now running.