Cloudron Forum

@andreasdueren aye, thanks for checking it out!

@andreasdueren do you have plans or even already tried adding something like https://hermes-workspace.com/ to the package?

@james today it was only one, lets see, maybe it was a glitch after all

Topic says it all, the only place where not the username is shown to select users for accessing an app or email accounts is during the installation of a new app - it shows the Display/Full name instead (also in the profile it says "Display name" and in the users setting it says "Full name", could be unified to throw out one of those strings).

unrelated, wanted to set this topic as a question, but it shows this and it won't change:

I gave a user operator rights to access SFTP in a LAMP app and if he clicks on the SFTP Access button in the info tab of the app, nothing happens. Browser console says

Object { status: 403, body: {…} }
​body: Object { status: "Forbidden", message: "role 'admin' is required but user has only 'user'" }
​status: 403

Not sure if intentional, but would be great if they were able to see the credentials.

@james thanks, looks okay in there. I'll do some more investigating, I just set a different time and it got only triggered once. Any idea why it might be doing it multiple times at 14:00?

@james exactly, app configuration -> cron. is there a place where all those cronjobs are collected to see if there are duplicate entries?

I have a Managed WordPress app which I use for weekly disk usage stats. The cronjob looks like this:

0 14 * * SUN export root_space=$(df -h | grep '/$'); export root_usage=$(echo $root_space | awk '{ print int($5) }'); curl -H "Authorization: Bearer xyz" -H "Title: Weekly disk usage report" -H "Priority: low" -H "Tags: loudspeaker" -X POST --data "Servername disk usage: $root_usage%" https://ntfy.example.com/df-alert >/dev/null 2>&1

I'm using the same thing on a few more servers and on those it is only sent only once, but this specific server usually runs twice, today even three times in a row. Where do I check if there are duplicates somewhere? Is there a global crontab which collects the apps' jobs?

App logs look like this:

Aug 16 14:00:10 => Run cron job
Aug 16 14:00:11 Success: Executed a total of 0 cron events.
Aug 16 14:00:19 {"id":"xxx","time":1786881619,"expires":1786924819,"event":"message","topic":"df-alert","title":"..."
Aug 16 14:00:20 - - - [16/Aug/2026:12:00:20 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Aug 16 14:00:30 - - - [16/Aug/2026:12:00:30 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Aug 16 14:00:37 {"id":"yyy","time":1786881637,"expires":1786924837,"event":"message","topic":"df-alert","title":"..."
Aug 16 14:00:40 - - - [16/Aug/2026:12:00:40 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Aug 16 14:00:43 {"id":"zzz","time":1786881643,"expires":1786924843,"event":"message","topic":"df-alert","title":"..."
Aug 16 14:00:50 - - - [16/Aug/2026:12:00:50 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"

No idea why they run more than once and with that much delay in between. Any suggestions on where to check?

@girish thanks for the reply! That's the thing, I'm not a 100% sure yet. It's a custom app that sends out 100+ emails (and growing) every few weeks/months and it hit twice the Connection denied. recipient rate limit exceeded and once Connection denied. connection rate limit exceeded. It wasn't great, because it wasn't clear which mails went through and which didn't (other than manually combing through the logs).

My guess would have been [rate_conn] and [rate_rcpt_host] for starters, but the quick fix (other than building a queue/delay/throttle which adds a lot of complexity) was to use Postmark directly instead of Cloudrons mail-server, so for this specific project this is "solved", but would still be a nice to have feature to adjust the limits in the settings.

Sorry to revive that old thread, but I ran into the same issues and need to up that limit. Will those changes survive restarts and Cloudron updates?

@andreasdueren thanks, I finally got it to work with private messages, channels seems to be more difficult. However, I also opted for the telegram option, less hassle

Not sure where we should post about community packages, so I'm hijacking this topic

First of all, thanks for the package @andreasdueren!

Quick question: did you try/manage to connect to an encrypted Matrix channel? Is it possible that we're missing the mautrix[encryption] package?

Yep, redis is up and running (also says so in the services tab):

Jul 02 12:56:10 13:C 02 Jul 2026 10:56:10.580 * Configuration loaded
Jul 02 12:56:10 13:C 02 Jul 2026 10:56:10.580 * Redis version=8.4.0, bits=64, commit=00000000, modified=1, pid=13, just started
Jul 02 12:56:10 13:C 02 Jul 2026 10:56:10.580 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.580 * Increased maximum number of open files to 10032 (it was originally set to 1024).
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.580 * monotonic clock: POSIX clock_gettime
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 # Failed to write PID file: Permission denied
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * Loading RDB produced by version 8.4.0
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * RDB age 5188 seconds
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * RDB memory usage when created 1.08 Mb
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * Running mode=standalone, port=6379.
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * Server initialized
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.582 * DB loaded from disk: 0.001 seconds
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.582 * Done loading RDB, keys loaded: 3, keys expired: 1.
Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.582 * Ready to accept connections tcp
Jul 02 12:56:10 2026-07-02 10:56:10,573 INFO spawned: 'redis' with pid 13
Jul 02 12:56:10 2026-07-02 10:56:10,574 INFO spawned: 'redis-service' with pid 14
Jul 02 12:56:10 Redis service endpoint listening on http://:::3000
Jul 02 12:56:11 2026-07-02 10:56:11,645 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Jul 02 12:56:11 2026-07-02 10:56:11,645 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

The errors only start to show up, when you access the site.

I've just updated my Open WebUI to 0.10.1 and the log is being spammed with this:

Jul 02 11:07:06 Cannot receive from redis... retrying in 1 secs
Jul 02 11:07:06 2026-07-02 09:07:06.757 | ERROR    | socketio.async_redis_manager:_redis_listen_with_retries:159 - Cannot receive from redis... retrying in 1 secs
Jul 02 11:07:12 Cannot receive from redis... retrying in 1 secs
Jul 02 11:07:12 2026-07-02 09:07:12.770 | ERROR    | socketio.async_redis_manager:_redis_listen_with_retries:159 - Cannot receive from redis... retrying in 1 secs
Jul 02 11:07:18 Cannot receive from redis... retrying in 1 secs

Not sure what changed, since the redis config wasn't touched or if this has a negative impact, just wanted to let you know.

1. That I know, but how would I get the second backup site to include those? Eventually I'll switch to the second backup as primary and lose the secondary one when they're in sync.

2. Right, but why does it work with the Storagebox and not MinIO, does that require more resources?

Two things:

I have a Cloudron (9.1.7) with two backup destinations, one MinIO and a Hetzner Storagebox. Both are set up to backup the same things every day, 2 hours apart.

1. For whatever reason the MinIO backup (which was the default and only backup for years) lists also stopped apps even though they're not included in the backup, both in size and # of apps.

Screenshot:

2. When trying to do an integrity check on the MinIO backup, it says it crashed due to oom (ran out of memory or terminated). The server has plenty of RAM and the Storagebox integrity check works without problems.

May 14 12:32:47 tasks: startTask - starting task 12627 with options {}. logs at /home/yellowtent/platformdata/logs/tasks/12627.log
May 14 12:32:47 tasks: updating task 12627 with: {"pending":false}
May 14 12:32:47 shell: tasks: /usr/bin/sudo --non-interactive -E /home/yellowtent/box/src/scripts/starttask.sh 12627 /home/yellowtent/platformdata/logs/tasks/12627.log 0 400 0
May 14 12:32:50 apphealthmonitor: app health: 25 running / 5 stopped / 0 unresponsive
May 14 12:32:52 shell: tasks: /usr/bin/sudo --non-interactive -E /home/yellowtent/box/src/scripts/starttask.sh 12627 /home/yellowtent/platformdata/logs/tasks/12627.log 0 400 0 errored with code 9 and signal null timeout false terminated false - stdout: "Service box-task-12627 failed to run
Service box-task-12627 finished with exit code 2 and status 9
" - stderr: "Running as unit: box-task-12627.service; invocation ID: 7db618c2df95465c8db4534413f4f106
Finished with result: oom-kill
Main processes terminated with: code=killed/status=KILL
Service runtime: 4.670s
CPU time consumed: 3.777s
Memory peak: 400.0M
Memory swap peak: 55.7M
"
May 14 12:32:52 tasks: startTask: 12627 done. error: {
  message: 'Task 12627 ran out of memory or terminated',
  code: 'crashed'
}
May 14 12:32:52 tasks: setCompleted - 12627: {"error":{"message":"Task 12627 ran out of memory or terminated","code":"crashed"}}
May 14 12:32:52 tasks: updating task 12627 with: {"completed":true,"error":{"message":"Task 12627 ran out of memory or terminated","code":"crashed"}}
May 14 12:32:52 backups: startIntegrityCheck: task error. Task 12627 ran out of memory or terminated

Could be that those 2 issues are related.

ah thanks @joseph, haven't tried that! https://docs.cloudron.io/packaging/cli/#cicd needs an update then

My build pipeline crashed because cloudron exec wouldn't accept --server and --token anymore on the latest CLI version. Is that by design or a regression?

cloudron exec --app example.com --server my.example.com --token $CLOUDRON_TOKEN -- rm -rf /app/data/trash/* comes back with error: unknown option '--server'. I downgraded from v8.2.3 to v8.0.0 and it's working again. If something changed, what would be the right way to make this work again?

@luckow Thanks for testing, that one was actually by design I just added an override for max scanned pages (15k should do it), please rescan. Also, don't forget to set a higher crawl rate on larger pages (if there's no throttle), that will improve the speed significantly