NCKNE
Posts
-
GitLab not starting. -
GitLab not starting.Fixed by entering recovery mode of the app and setting
mem_gb=$(( $(cat /sys/fs/cgroup/memory.max) / 1073741824 ))to
# mem_gb=$(( $(cat /sys/fs/cgroup/memory.max) / 1073741824 )) mem_gb=10in /home/git/start.sh
and running start.sh manually (still in recovery mode).
Seems like a bug though that should be fixed in the package.
-
GitLab not starting.Latest version of the GitLab container (but also previous version tested) does not start anymore. Logs see logs at the end. I assume the lines
/home/git/start.sh: line 216: / 1073741824 : syntax error: operand expected (error token is "/ 1073741824 ") Jul 09 13:12:59 /home/git/start.sh: line 217: mem_gb: unbound variablein the container log might be the root cause.
Can anyone help getting GitLab running again?
2026-07-09T11:08:17.080Z box:apptask startApp: starting container 2026-07-09T11:08:17.443Z box:tasks updating task 17001 with: {"percent":90,"message":"Configuring reverse proxy"} 2026-07-09T11:08:17.447Z box:tasks updating task 17001 with: {"percent":100,"message":"Done"} 2026-07-09T11:08:17.457Z box:tasks setCompleted - 17001: {"result":null,"error":null,"percent":100} 2026-07-09T11:08:17.457Z box:tasks updating task 17001 with: {"completed":true,"result":null,"error":null,"percent":100} 2026-07-09T11:08:17.462Z Exiting with code 0 2026-07-09T11:08:17.462Z box:taskworker Task took 210.669 seconds 2026-07-09T11:08:17Z ==> Copying schema file 2026-07-09T11:08:17Z ==> Fixing secrets 2026-07-09T11:08:17Z ==> Initializing gitlab shell 2026-07-09T11:08:17Z ==> Reusing existing host keys 2026-07-09T11:08:17Z ==> Setting up tmp 2026-07-09T11:08:18Z ==> Fixing permissions 2026-07-09T11:08:19Z ==> Creating pg_trgm extension 2026-07-09T11:08:19Z ==> Upgrading existing db 2026-07-09T11:08:19Z NOTICE: extension "pg_trgm" already exists, skipping 2026-07-09T11:08:20.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:08:24Z [0m[33mBundler will use `/tmp/bundler20260709-172-26om0y172' as your home directory temporarily. 2026-07-09T11:08:24Z [33m`/home/git` is not writable. 2026-07-09T11:08:30.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:08:40.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:08:42Z 2026-07-09T11:08:42Z 2026-07-09T11:08:42Z 2026-07-09T11:08:42Z 2026-07-09T11:08:42Z [0m 2026-07-09T11:08:42Z [0m 2026-07-09T11:08:42Z [0m[31m 2026-07-09T11:08:42Z [31m 2026-07-09T11:08:42Z ****************************************************************************** 2026-07-09T11:08:42Z ****************************************************************************** 2026-07-09T11:08:42Z ****************************************************************************** 2026-07-09T11:08:42Z ****************************************************************************** 2026-07-09T11:08:42Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:08:42Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:08:42Z You are using PostgreSQL 16.11 for the ci database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:08:42Z You are using PostgreSQL 16.11 for the main database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:08:42Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:08:42Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:08:42Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:08:42Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:08:42Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:08:42Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:08:42Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:08:42Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:08:42Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:08:42Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:08:42Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ 2026-07-09T11:08:42Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ 2026-07-09T11:08:50.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:09:00.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:09:01Z main: == [advisory_lock_connection] object_id: 56440, pg_backend_pid: 419 2026-07-09T11:09:02Z main: == [advisory_lock_connection] object_id: 56440, pg_backend_pid: 419 2026-07-09T11:09:07Z ==> Installing gitlab shell 2026-07-09T11:09:07Z ==> Synchronizing ssh keys 2026-07-09T11:09:07Z chmod 700 /home/git/.ssh: OK 2026-07-09T11:09:07Z mkdir -p /home/git/.ssh: OK 2026-07-09T11:09:10.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:09:12Z [0m[33mBundler will use `/tmp/bundler20260709-277-4fesnx277' as your home directory temporarily. 2026-07-09T11:09:12Z [33m`/home/git` is not writable. 2026-07-09T11:09:20.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:09:30.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:09:31Z 2026-07-09T11:09:31Z 2026-07-09T11:09:31Z 2026-07-09T11:09:31Z 2026-07-09T11:09:31Z [0m 2026-07-09T11:09:31Z [0m 2026-07-09T11:09:31Z [0m[31m 2026-07-09T11:09:31Z [31m 2026-07-09T11:09:31Z ****************************************************************************** 2026-07-09T11:09:31Z ****************************************************************************** 2026-07-09T11:09:31Z ****************************************************************************** 2026-07-09T11:09:31Z ****************************************************************************** 2026-07-09T11:09:31Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:09:31Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:09:31Z You are using PostgreSQL 16.11 for the ci database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:09:31Z You are using PostgreSQL 16.11 for the main database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:09:31Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:09:31Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:09:31Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:09:31Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:09:31Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:09:31Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:09:31Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:09:31Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:09:31Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:09:31Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:09:31Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ 2026-07-09T11:09:31Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ 2026-07-09T11:09:40.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:09:49Z [34mDo you want to continue (yes/no)? [0m 2026-07-09T11:09:49Z /home/git/start.sh: line 216: / 1073741824 : syntax error: operand expected (error token is "/ 1073741824 ") 2026-07-09T11:09:49Z /home/git/start.sh: line 217: mem_gb: unbound variable 2026-07-09T11:09:49Z This task will now rebuild the authorized_keys file. 2026-07-09T11:09:49Z You will lose any data stored in the authorized_keys file. 2026-07-09T11:09:49Z cat: /sys/fs/cgroup/memory.max: No such file or directory 2026-07-09T11:09:51.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:09:51Z ==> Copying schema file 2026-07-09T11:09:51Z ==> Fixing secrets 2026-07-09T11:09:51Z ==> Initializing gitlab shell 2026-07-09T11:09:51Z ==> Reusing existing host keys 2026-07-09T11:09:51Z ==> Setting up tmp 2026-07-09T11:09:52Z ==> Creating pg_trgm extension 2026-07-09T11:09:52Z ==> Fixing permissions 2026-07-09T11:09:52Z ==> Upgrading existing db 2026-07-09T11:09:52Z NOTICE: extension "pg_trgm" already exists, skipping 2026-07-09T11:09:57Z [0m[33mBundler will use `/tmp/bundler20260709-172-139zlf172' as your home directory temporarily. 2026-07-09T11:09:57Z [33m`/home/git` is not writable. 2026-07-09T11:10:00.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:10:10.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:10:16Z 2026-07-09T11:10:16Z 2026-07-09T11:10:16Z [0m 2026-07-09T11:10:16Z [0m[31m 2026-07-09T11:10:16Z ****************************************************************************** 2026-07-09T11:10:16Z ****************************************************************************** 26-07-09T11:10:16Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:10:16Z You are using PostgreSQL 16.11 for the main database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:10:16Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:10:16Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:10:16Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:10:16Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:10:16Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:10:16Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ 2026-07-09T11:10:17Z 2026-07-09T11:10:17Z 2026-07-09T11:10:17Z [0m 2026-07-09T11:10:17Z [31m 2026-07-09T11:10:17Z ****************************************************************************** 2026-07-09T11:10:17Z ****************************************************************************** 2026-07-09T11:10:17Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:10:17Z You are using PostgreSQL 16.11 for the ci database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:10:17Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:10:17Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:10:17Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:10:17Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:10:17Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:10:17Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ 2026-07-09T11:10:20.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:10:30.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:10:36Z main: == [advisory_lock_connection] object_id: 56440, pg_backend_pid: 448 2026-07-09T11:10:36Z main: == [advisory_lock_connection] object_id: 56440, pg_backend_pid: 448 2026-07-09T11:10:40.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:10:42Z ==> Installing gitlab shell 2026-07-09T11:10:42Z ==> Synchronizing ssh keys 2026-07-09T11:10:42Z chmod 700 /home/git/.ssh: OK 2026-07-09T11:10:42Z mkdir -p /home/git/.ssh: OK 2026-07-09T11:10:47Z [0m[33mBundler will use `/tmp/bundler20260709-278-im9yai278' as your home directory temporarily. 2026-07-09T11:10:47Z [33m`/home/git` is not writable. 2026-07-09T11:10:50.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:11:00.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:11:06Z 2026-07-09T11:11:06Z 2026-07-09T11:11:06Z 2026-07-09T11:11:06Z 2026-07-09T11:11:06Z [0m 2026-07-09T11:11:06Z [0m 2026-07-09T11:11:06Z [0m[31m 2026-07-09T11:11:06Z [31m 2026-07-09T11:11:06Z ****************************************************************************** 2026-07-09T11:11:06Z ****************************************************************************** 2026-07-09T11:11:06Z ****************************************************************************** 2026-07-09T11:11:06Z ****************************************************************************** 2026-07-09T11:11:06Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:11:06Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:11:06Z You are using PostgreSQL 16.11 for the ci database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:11:06Z You are using PostgreSQL 16.11 for the main database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:11:06Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:11:06Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:11:06Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:11:06Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:11:06Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:11:06Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:11:06Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:11:06Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:11:06Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:11:06Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:11:06Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ 2026-07-09T11:11:06Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ 2026-07-09T11:11:10.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:11:20.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:11:24Z [34mDo you want to continue (yes/no)? [0m 2026-07-09T11:11:24Z /home/git/start.sh: line 216: / 1073741824 : syntax error: operand expected (error token is "/ 1073741824 ") 2026-07-09T11:11:24Z /home/git/start.sh: line 217: mem_gb: unbound variable 2026-07-09T11:11:24Z This task will now rebuild the authorized_keys file. 2026-07-09T11:11:24Z You will lose any data stored in the authorized_keys file. 2026-07-09T11:11:24Z cat: /sys/fs/cgroup/memory.max: No such file or directory 2026-07-09T11:11:26Z ==> Copying schema file 2026-07-09T11:11:26Z ==> Fixing secrets 2026-07-09T11:11:26Z ==> Initializing gitlab shell 2026-07-09T11:11:26Z ==> Reusing existing host keys 2026-07-09T11:11:26Z ==> Setting up tmp 2026-07-09T11:11:27Z ==> Creating pg_trgm extension 2026-07-09T11:11:27Z ==> Fixing permissions 2026-07-09T11:11:27Z ==> Upgrading existing db 2026-07-09T11:11:27Z NOTICE: extension "pg_trgm" already exists, skipping 2026-07-09T11:11:30.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:11:32Z [0m[33mBundler will use `/tmp/bundler20260709-171-9wygvk171' as your home directory temporarily. 2026-07-09T11:11:32Z [33m`/home/git` is not writable. 2026-07-09T11:11:40.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:11:50.000Z => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.166:80 2026-07-09T11:11:50Z 13:M 09 Jul 2026 11:11:50.092 * 10 changes in 300 seconds. Saving... 2026-07-09T11:11:50Z 13:M 09 Jul 2026 11:11:50.096 * Background saving started by pid 40 2026-07-09T11:11:50Z 13:M 09 Jul 2026 11:11:50.198 * Background saving terminated with success 2026-07-09T11:11:50Z 40:C 09 Jul 2026 11:11:50.136 * DB saved on disk 2026-07-09T11:11:50Z 40:C 09 Jul 2026 11:11:50.137 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB 2026-07-09T11:11:51Z 2026-07-09T11:11:51Z 2026-07-09T11:11:51Z 2026-07-09T11:11:51Z 2026-07-09T11:11:51Z [0m 2026-07-09T11:11:51Z [0m 2026-07-09T11:11:51Z [0m[31m 2026-07-09T11:11:51Z [31m 2026-07-09T11:11:51Z ****************************************************************************** 2026-07-09T11:11:51Z ****************************************************************************** 2026-07-09T11:11:51Z ****************************************************************************** 2026-07-09T11:11:51Z ****************************************************************************** 2026-07-09T11:11:51Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:11:51Z Please upgrade your environment to a supported PostgreSQL version. See 2026-07-09T11:11:51Z You are using PostgreSQL 16.11 for the ci database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:11:51Z You are using PostgreSQL 16.11 for the main database, but this version of GitLab requires PostgreSQL >= 17. 2026-07-09T11:11:51Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:11:51Z https://docs.gitlab.com/ee/install/requirements.html#database for details. 2026-07-09T11:11:51Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:11:51Z ██ ██ █████ ██████ ███ ██ ██ ███ ██ ██████ 2026-07-09T11:11:51Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:11:51Z ██ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██ ██ 2026-07-09T11:11:51Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:11:51Z ██ █ ██ ███████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ███ 2026-07-09T11:11:51Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:11:51Z ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ 2026-07-09T11:11:51Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ 2026-07-09T11:11:51Z ███ ███ ██ ██ ██ ██ ██ ████ ██ ██ ████ ██████ -
Install Additional Python Module for OpenWebUIInstallation of additional packages would be great! Would a quick fix be to make the directory "/app/code/venv/lib/python3.12/site-packages/" writable in the cloudron app (eg. symlink to a /app/data/site-packages directory)?
-
EntraID / AzureAD LDAP wrapper@JLX89 said in EntraID / AzureAD LDAP wrapper:
How about just using an Enterprise App with SCIM Provisioning?
That would be great

-
Potential dataloss in Memos with Cloudron 8.3.0 upgrade?Oh yeah, I had an issue with Nextcloud as well after the upgrade. Forgot to mention that. Same thing, some table (I think it was oc_appinfo) could not be found. A restore of the backup right before the upgrade fixed that for me as well.
Same for Cal, Outline, Documenso, Linkwarden and Formbricks by the way. The app started but with a fresh database. A restore brought all back.
I am very happy with the great backup/restore concept and automated backups before an upgrade. Works so great. -
Potential dataloss in Memos with Cloudron 8.3.0 upgrade?Great! Must have been something on my server then - all good, I was able to restore from a previous backup and it was just test data anyways... Thanks for checking!
-
Potential dataloss in Memos with Cloudron 8.3.0 upgrade?I configured access to the old backups and restored one before the upgrade to 8.3.0. All data is back now! Not sure what happened, but if it doesn't occur in your CI testing it might just have been something strange on my system.
-
Potential dataloss in Memos with Cloudron 8.3.0 upgrade?@girish Thanks for testing. I only had data for one user using OIDC. Another reason might be that the OIDC mapping is not working as before?
-
Potential dataloss in Memos with Cloudron 8.3.0 upgrade?Just a quick observation: after upgrading from Cloudron 8.2.x to 8.3.0, all data in Memos for my OIDC user has vanished. No problem for me as I was just starting to use it and only had some test data in Memos. Could this be related to the database upgrade of postgresql? Unfortunately, I cannot assist in debugging as I migrated Cloudron to a beefier server (always amazing how simple and elegant that ist!) in the meantime and do not have easy access to the old logs / backups / etc.
-
Tika ServerIt would be awesome if openwebui could use the Cloudron Tika server.
-
Weird email log probably spam attack?You can also follow this great guide and set up an automated blocklist update:
https://forum.cloudron.io/topic/3795/firewall-spamassassin-automatic-list-update/41?_=1740739173375Might mitigate some (few) of these annoying spam attacks.
-
glauth ldap backend@joseph said in glauth ldap backend:
@NCKNE were you able to run that command? trying to see if we can fix the code to simply auto-detect this and disable paging automatically (instead of adding an option) . my understanding is that paging is optional to ldap servers.
That's a great idea! I ran the command but got the following response:
root@ldap-wrapper-r90:~# ldapsearch -x -s base -b "" supportedControl -H ldap://localhost:13389 # extended LDIF # # LDAPv3 # base <> with scope baseObject # filter: (objectclass=*) # requesting: supportedControl # # domain.de dn: dc=domain,dc=de # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 -
glauth ldap backendYes, although I am not using glauth for LDAP, the server does not support paging. There seem to be various configurations that do not support paging, so an option to disable it in the Cloudron LDAP sync config would be nice.
-
glauth ldap backendUpdate: Changing all occurrences of
paged: trueto
paged: falsein
/home/yellowtent/box/src/externalldap.jsMakes LDAP Sync work. Maybe adding a GUI option for paging in the LDAP sync configuration settings would be a good idea?
-
glauth ldap backendI am encountering the same error ("missing paged control") when connecting to a ldapjs server:
2025-02-25T07:37:57.542Z box:taskworker Starting task 10372. Logs are at /home/yellowtent/platformdata/logs/tasks/10372.log 2025-02-25T07:37:57.566Z box:taskworker Running task of type syncExternalLdap 2025-02-25T07:37:57.566Z box:tasks update 10372: {"percent":10,"message":"Starting ldap user sync"} 2025-02-25T07:37:59.860Z box:taskworker Task took 2.366 seconds 2025-02-25T07:37:59.860Z box:tasks setCompleted - 10372: {"result":null,"error":{"stack":"BoxError: missing paged control\n at SearchPager.<anonymous> (/home/yellowtent/box/src/externalldap.js:162:48)\n at SearchPager.emit (node:events:519:28)\n at SearchPager.emit (/home/yellowtent/box/node_modules/ldapjs/lib/corked_emitter.js:44:33)\n at SearchPager._onEnd (/home/yellowtent/box/node_modules/ldapjs/lib/client/search_pager.js:103:12)\n at EventEmitter.emit (node:events:519:28)\n at sendResult (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1194:22)\n at messageCallback (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1222:16)\n at Parser.onMessage (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:888:14)\n at Parser.emit (node:events:519:28)\n at Parser.write (/home/yellowtent/box/node_modules/ldapjs/lib/messages/parser.js:107:8)","name":"BoxError","reason":"External Error","details":{},"message":"missing paged control","nestedError":{"stack":"PagedError: missing paged control\n at SearchPager._onEnd (/home/yellowtent/box/node_modules/ldapjs/lib/client/search_pager.js:93:17)\n at EventEmitter.emit (node:events:519:28)\n at sendResult (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1194:22)\n at messageCallback (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1222:16)\n at Parser.onMessage (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:888:14)\n at Parser.emit (node:events:519:28)\n at Parser.write (/home/yellowtent/box/node_modules/ldapjs/lib/messages/parser.js:107:8)\n at end (/home/yellowtent/box/node_modules/ldapjs/lib/messages/parser.js:62:36)\n at Parser.write (/home/yellowtent/box/node_modules/ldapjs/lib/messages/parser.js:108:10)\n at Socket.onData (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:875:22)","name":"PagedError","message":"missing paged control"}}} 2025-02-25T07:37:59.861Z box:tasks update 10372: {"percent":100,"result":null,"error":{"stack":"BoxError: missing paged control\n at SearchPager.<anonymous> (/home/yellowtent/box/src/externalldap.js:162:48)\n at SearchPager.emit (node:events:519:28)\n at SearchPager.emit (/home/yellowtent/box/node_modules/ldapjs/lib/corked_emitter.js:44:33)\n at SearchPager._onEnd (/home/yellowtent/box/node_modules/ldapjs/lib/client/search_pager.js:103:12)\n at EventEmitter.emit (node:events:519:28)\n at sendResult (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1194:22)\n at messageCallback (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1222:16)\n at Parser.onMessage (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:888:14)\n at Parser.emit (node:events:519:28)\n at Parser.write (/home/yellowtent/box/node_modules/ldapjs/lib/messages/parser.js:107:8)","name":"BoxError","reason":"External Error","details":{},"message":"missing paged control","nestedError":{"stack":"PagedError: missing paged control\n at SearchPager._onEnd (/home/yellowtent/box/node_modules/ldapjs/lib/client/search_pager.js:93:17)\n at EventEmitter.emit (node:events:519:28)\n at sendResult (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1194:22)\n at messageCallback (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1222:16)\n at Parser.onMessage (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:888:14)\n at Parser.emit (node:events:519:28)\n at Parser.write (/home/yellowtent/box/node_modules/ldapjs/lib/messages/parser.js:107:8)\n at end (/home/yellowtent/box/node_modules/ldapjs/lib/messages/parser.js:62:36)\n at Parser.write (/home/yellowtent/box/node_modules/ldapjs/lib/messages/parser.js:108:10)\n at Socket.onData (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:875:22)","name":"PagedError","message":"missing paged control"}}} BoxError: missing paged control at SearchPager.<anonymous> (/home/yellowtent/box/src/externalldap.js:162:48) at SearchPager.emit (node:events:519:28) at SearchPager.emit (/home/yellowtent/box/node_modules/ldapjs/lib/corked_emitter.js:44:33) at SearchPager._onEnd (/home/yellowtent/box/node_modules/ldapjs/lib/client/search_pager.js:103:12) at EventEmitter.emit (node:events:519:28) at sendResult (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1194:22) at messageCallback (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:1222:16) at Parser.onMessage (/home/yellowtent/box/node_modules/ldapjs/lib/client/client.js:888:14) at Parser.emit (node:events:519:28) at Parser.write (/home/yellowtent/box/node_modules/ldapjs/lib/messages/parser.js:107:8)The ldapjs server that is being queried logs the following in debug mode:
DEBUG: 2025-02-25T07:37:59.816Z: %s: sending: %j 1.2.3.4:54938 { status: 0, matchedDN: '', diagnosticMessage: '', referrals: [] } TRACE: 2025-02-25T07:37:59.883Z: %s shutdown 1.2.3.4:54938 TRACE: 2025-02-25T07:37:59.884Z: %s close; had_err=%j 1.2.3.4:54938 falseCould this be related to paging? Can paging be disabled in Cloudron to test if that is the cause?
-
EntraID / AzureAD LDAP wrapper@joseph said in EntraID / AzureAD LDAP wrapper:
@NCKNE said in EntraID / AzureAD LDAP wrapper:
Entra ID / Azure AD is not LDAP
TIL
Had no clue, ignore my previous comment then. Just read about it a little more and it seems you need something called Azure AD DS per https://www.reddit.com/r/sysadmin/comments/120e71z/ldaps_with_azure_ad_tenant_bundled_with_office_365/Yeah, but the Azure AD DS you mentioned is very complex and expensive (licensing costs). I just thought since the topic had come up a few time, native support of Entra ID / Azure AD might be something to consider for the future.
-
EntraID / AzureAD LDAP wrapper@joseph said in EntraID / AzureAD LDAP wrapper:
AD support seems to be something we should add directly to Cloudron's existing LDAP server, if this is deemed useful. Incidentally, Cloudron's ldap server is also based on ldapjs.
Entra ID / Azure AD is not LDAP… that’s why either a wrapper like above is needed or Cloudron could natively implement Entra ID support (as many other apps do) and connect it to the Cloudron internal directory.
-
EntraID / AzureAD LDAP wrapperThe topic has come up several times in the forum in the past: Is there an easy way to connect the Cloudron user directory to Microsoft Entra ID (formerly Azure AD) for a same signin scenario? Microsoft offers the Entra ID Domain Services with LDAP, but it involves a very complex and cost intensive setup.
I have been using the "Azure AD LDAP Wrapper" in the past which uses the Microsoft Graph API and provides an LDAP endpoint for Entra ID:
https://ahaenggli.github.io/AzureAD-LDAP-wrapper/installation/run-ldap-wrapper/The project is quite simple and easy to install using docker or nodejs directly. I am currently running it on a seperate server with firewall rules to allow only specific ip addresses to access the LDAP port. Now, wouldn't be great if this could run as a Cloudron app itself? If it was published on the app store, one would only need to provide the Azure App registration data in an env-file and could bind the Cloudron directory to a local (private) LDAP port on the same server.
Well, I am new to packaging apps for Cloudron and have no idea how to package an app without a web interface. Heath checks would need to check the LDAP port and not HTTP, etc. Is this even a scenario wanted by the @staff?
If so, I could give packaging a try and do some testing, but would need some pointers if this can/should be realized as an app within Cloudron as it would need to expose a custom LDAP port to the internal docker stack.
-
Forward Email with SES, Got "554 Message rejected: Email address is not verified"If SRS is not an option (or not obeyed by Gmail) you can look into some advanced sieve stuff:
https://doc.dovecot.org/2.3/configuration_manual/sieve/configuring_auto_forward_sender_address/