Cloudron Forum

It was indeed a plugin conflict, which I was able to observe an error for in the wordpress debug logs. The manual wordpress update went smoothly after removing that plugin.

@d19dotca yes, but there's an error when updating, which I assumed was because of Cloudron stuff, but perhaps updates are supposed to happen manually in wordpress and the "critical error" I get when updating is actually related to plugin conflicts and the like?

For some reason my wordpress version isn't getting updated when cloudron does the app update.

I'm not seeing stuff in the app logs about it - any ideas?
it is a multisite

Is the best option to SFTP replace the files?

https://join.piefed.social/

it seems like maybe the issues is my device occasionally running out of space crashing postgres - does that check out?

I'll try moving my docker images to another drive to preven that issue as space use seems to fluctuate drastically...

I did just catch it at 70%...
My MYSQL memory limit is set at 4.125GB - I bumped postgresql up to 5GB - is that likely to be enough or should I go higher?
The box has 32GB of memory and a big swap so I think it can handle pretty high memory usage.

Ok, it seemed running the /home/yellowtent/box/setup/start.sh to trigger the migration after restoring the database (because of the ERROR 1046 (3D000) at line 22: No database selected i needed to add these two lines to the dump file:

CREATE DATABASE box;
USE box;

Then it was able to backup the database and run the migration.

@joseph the dashboard had me reconfigure the domain, and then the box was empty - no apps or settings - meanwhile everything was running in the background.

I've tried recovering the last database dump, and also from backups, but the error I was getting was interrupting it.

I needed to add the database name into the mysql dump file manually, but now i'm getting:

2025-01-23T13:50:49.964Z box:server            Cloudron 8.2.3  
2025-01-23T13:50:49.964Z box:server ==========================================
2025-01-23T13:50:49.964Z box:platform initialize: start platform
2025-01-23T13:50:49.994Z box:tasks stopAllTasks: stopping all tasks
2025-01-23T13:50:49.994Z box:shell tasks /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2025-01-23T13:50:50.039Z box:shell All tasks stopped

2025-01-23T13:50:50.050Z Error: Error starting server: {"name":"BoxError","reason":"Database Error","details":{},"message":"ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client","nestedError":{"code":"ER_NOT_SUPPORTED_AUTH_MODE","errno":1251,"sqlMessage":"Client does not support authentication protocol requested by server; consider upgrading MySQL client","sqlState":"08004","fatal":true},"code":"ER_NOT_SUPPORTED_AUTH_MODE","sqlMessage":"Client does not support authentication protocol requested by server; consider upgrading MySQL client"}
2025-01-23T13:50:50.050Z     at main (/home/yellowtent/box/box.js:58:41)
2025-01-23T13:50:50.050Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

well that did something weird...

it had me setup a new box but somehow the apps are still running in the background...

Maybe I lost the backup I had tried to recover somehow?

When does the migration run? what is that a part of?

I had recently upgraded Cloudron...

I want to get my old admin settings back but the recovery instructions seem to be failing...

Tried to restor the box.mqysl database in mysql via the instructions here:
https://docs.cloudron.io/troubleshooting/

Now running into more issues:

there was this error while trying to import that database:

ERROR 1046 (3D000) at line 22: No database selected

And currently having this issue with starting box:

2025-01-22T14:15:44.936Z box:server ==========================================
2025-01-22T14:15:44.937Z box:server            Cloudron 8.2.3  
2025-01-22T14:15:44.937Z box:server ==========================================
2025-01-22T14:15:44.937Z box:platform initialize: start platform
2025-01-22T14:15:44.968Z box:tasks stopAllTasks: stopping all tasks
2025-01-22T14:15:44.968Z box:shell tasks /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2025-01-22T14:15:45.003Z box:shell All tasks stopped

2025-01-22T14:15:45.023Z Error: Error starting server: {"name":"BoxError","reason":"Database Error","details":{},"message":"ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client","nestedError":{"code":"ER_NOT_SUPPORTED_AUTH_MODE","errno":1251,"sqlMessage":"Client does not support authentication protocol requested by server; consider upgrading MySQL client","sqlState":"08004","fatal":true},"code":"ER_NOT_SUPPORTED_AUTH_MODE","sqlMessage":"Client does not support authentication protocol requested by server; consider upgrading MySQL client"}
2025-01-22T14:15:45.023Z     at main (/home/yellowtent/box/box.js:58:41)
2025-01-22T14:15:45.023Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

which database would this be?

@joseph yes, it was 2GB plus - I haven't managed to catch it maxing out of memory since then though it's possible

I'm gettin gthis error on repeat:

2025-01-22T13:47:11.689Z box:server ==========================================
2025-01-22T13:47:11.690Z box:server            Cloudron 8.2.3  
2025-01-22T13:47:11.690Z box:server ==========================================
2025-01-22T13:47:11.690Z box:platform initialize: start platform
2025-01-22T13:47:11.721Z box:tasks stopAllTasks: stopping all tasks
2025-01-22T13:47:11.722Z box:shell tasks /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2025-01-22T13:47:11.752Z box:shell All tasks stopped

2025-01-22T13:47:11.765Z Error: Error starting server: {"name":"BoxError","reason":"Database Error","details":{},"message":"ER_NO_SUCH_TABLE: Table 'box.locks' doesn't exist","nestedError":{"code":"ER_NO_SUCH_TABLE","errno":1146,"sqlMessage":"Table 'box.locks' doesn't exist","sqlState":"42S02","index":0,"sql":"DELETE FROM locks"},"code":"ER_NO_SUCH_TABLE","sqlMessage":"Table 'box.locks' doesn't exist"}
2025-01-22T13:47:11.765Z     at main (/home/yellowtent/box/box.js:58:41)
2025-01-22T13:47:11.765Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

For some reason postgres keep crashing, and then mastodon and a few other apps, plus backups don't work until I go in an manually restart it.

It appears yellow in services.

backups error with:

Jan 15 03:05:54 box:tasks setCompleted - 6715: {"result":null,"error":{"stack":"BoxError: Unexpected response code or HTTP error when piping http://172.18.30.2:3000/databases/db04f262be1a1a40d1beed2fd1d95d0dfb/backup?access_token=426047e4ce5009e88eff393b292fafb1e64fad4736a2d78661ffc48f61327cb03e5d8ba67bada47dad087675e7dbd293291e8d58a0efacff0197dc5941bd71f0898b0cebe584d0ce31e9c9571f558df61a775cfeda9f85a52d1d8775ad1a51bb5e7e8e5f6ecfa81088b2b677857fe2b3bafbb21d6a9b2c8b9c843ac10e15456d to /home/yellowtent/appsdata/04f262be-1a1a-40d1-beed-2fd1d95d0dfb/postgresqldump: status 500\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1283:60)\n at ClientRequest.emit (node:events:519:28)\n at ClientRequest.emit (node:domain:488:12)\n at HTTPParser.parserOnIncomingClient (node:_http_client:702:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:118:17)\n at Socket.socketOnData (node:_http_client:544:22)\n at Socket.emit (node:events:519:28)\n at Socket.emit (node:domain:488:12)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)","name":"BoxError","reason":"Addons Error","details":{},"message":"Unexpected response code or HTTP error when piping http://172.18.30.2:3000/databases/db04f262be1a1a40d1beed2fd1d95d0dfb/backup?access_token=426047e4ce5009e88eff393b292fafb1e64fad4736a2d78661ffc48f61327cb03e5d8ba67bada47dad087675e7dbd293291e8d58a0efacff0197dc5941bd71f0898b0cebe584d0ce31e9c9571f558df61a775cfeda9f85a52d1d8775ad1a51bb5e7e8e5f6ecfa81088b2b677857fe2b3bafbb21d6a9b2c8b9c843ac10e15456d to /home/yellowtent/appsdata/04f262be-1a1a-40d1-beed-2fd1d95d0dfb/postgresqldump: status 500"}}
Jan 15 03:05:54 box:tasks update 6715: {"percent":100,"result":null,"error":{"stack":"BoxError: Unexpected response code or HTTP error when piping http://172.18.30.2:3000/databases/db04f262be1a1a40d1beed2fd1d95d0dfb/backup?access_token=426047e4ce5009e88eff393b292fafb1e64fad4736a2d78661ffc48f61327cb03e5d8ba67bada47dad087675e7dbd293291e8d58a0efacff0197dc5941bd71f0898b0cebe584d0ce31e9c9571f558df61a775cfeda9f85a52d1d8775ad1a51bb5e7e8e5f6ecfa81088b2b677857fe2b3bafbb21d6a9b2c8b9c843ac10e15456d to /home/yellowtent/appsdata/04f262be-1a1a-40d1-beed-2fd1d95d0dfb/postgresqldump: status 500\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1283:60)\n at ClientRequest.emit (node:events:519:28)\n at ClientRequest.emit (node:domain:488:12)\n at HTTPParser.parserOnIncomingClient (node:_http_client:702:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:118:17)\n at Socket.socketOnData (node:_http_client:544:22)\n at Socket.emit (node:events:519:28)\n at Socket.emit (node:domain:488:12)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)","name":"BoxError","reason":"Addons Error","details":{},"message":"Unexpected response code or HTTP error when piping http://172.18.30.2:3000/databases/db04f262be1a1a40d1beed2fd1d95d0dfb/backup?access_token=426047e4ce5009e88eff393b292fafb1e64fad4736a2d78661ffc48f61327cb03e5d8ba67bada47dad087675e7dbd293291e8d58a0efacff0197dc5941bd71f0898b0cebe584d0ce31e9c9571f558df61a775cfeda9f85a52d1d8775ad1a51bb5e7e8e5f6ecfa81088b2b677857fe2b3bafbb21d6a9b2c8b9c843ac10e15456d to /home/yellowtent/appsdata/04f262be-1a1a-40d1-beed-2fd1d95d0dfb/postgresqldump: status 500"}}
Jan 15 03:05:54 BoxError: Unexpected response code or HTTP error when piping http://172.18.30.2:3000/databases/db04f262be1a1a40d1beed2fd1d95d0dfb/backup?access_token=426047e4ce5009e88eff393b292fafb1e64fad4736a2d78661ffc48f61327cb03e5d8ba67bada47dad087675e7dbd293291e8d58a0efacff0197dc5941bd71f0898b0cebe584d0ce31e9c9571f558df61a775cfeda9f85a52d1d8775ad1a51bb5e7e8e5f6ecfa81088b2b677857fe2b3bafbb21d6a9b2c8b9c843ac10e15456d to /home/yellowtent/appsdata/04f262be-1a1a-40d1-beed-2fd1d95d0dfb/postgresqldump: status 500
Jan 15 03:05:54 at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1283:60)

error log in postgres says this (until restart):

backup: failed to backup database. Error: connect ECONNREFUSED ::1:5432
Jan 12 03:05:56 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
Jan 12 03:05:56 errno: -111,
Jan 12 03:05:56 code: 'ECONNREFUSED',
Jan 12 03:05:56 syscall: 'connect',
Jan 12 03:05:56 address: '::1',
Jan 12 03:05:56 port: 5432
Jan 12 03:05:56 }
Jan 13 03:03:18 [POST] /databases/db04f262be1a1a40d1beed2fd1d95d0dfb/backup
Jan 13 03:03:18 backup: failed to backup database. Error: connect ECONNREFUSED ::1:5432
Jan 13 03:03:18 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
Jan 13 03:03:18 errno: -111,
Jan 13 03:03:18 code: 'ECONNREFUSED',
Jan 13 03:03:18 syscall: 'connect',
Jan 13 03:03:18 address: '::1',
Jan 13 03:03:18 port: 5432
Jan 13 03:03:18 }
Jan 15 03:05:53 [POST] /databases/db04f262be1a1a40d1beed2fd1d95d0dfb/backup
Jan 15 03:05:54 backup: failed to backup database. Error: connect ECONNREFUSED ::1:5432
Jan 15 03:05:54 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
Jan 15 03:05:54 errno: -111,
Jan 15 03:05:54 code: 'ECONNREFUSED',
Jan 15 03:05:54 syscall: 'connect',
Jan 15 03:05:54 address: '::1',
Jan 15 03:05:54 port: 5432
Jan 15 03:05:54 }
Jan 17 13:23:35 [GET] /healthcheck
Jan 17 13:23:38 2025-01-17 18:23:38,590 WARN received SIGTERM indicating exit request
Jan 17 13:23:38 2025-01-17 18:23:38,602 INFO waiting for postgresql-service to die
Jan 17 13:23:39 2025-01-17 18:23:39,621 INFO stopped: postgresql-service (terminated by SIGTERM)```


What's up with this and how can i better troubleshoot address this?

this one (which I should have figured out earlier I think!) fixed collectd:
apt-get remove --auto-remove collectd-core
apt-get purge --auto-remove collectd-core
apt-get update
apt-get --yes install collectd

Then I also I had to run sudo /home/yellowtent/box/setup/start.sh

and we're up!

some stuff runs but the dashboard is broken and I can't for the life of met get Collectd to install properly...

troubleshooter starts cloudron and gets hung up on configuring collected:
2024-10-21T01:41:43 ==> start: Configuring collectd
A dependency job for collectd.service failed. See 'journalctl -xe' for details.

when installing various ways:

sudo apt install --fix-broken
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up collectd (5.12.0-17.1build2) ...
A dependency job for collectd.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript collectd, action "restart" failed.
○ collectd.service - Statistics collection and monitoring daemon
     Loaded: loaded (/usr/lib/systemd/system/collectd.service; enabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:collectd(1)
             man:collectd.conf(5)
             https://collectd.org

Oct 21 01:34:38 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:34:38 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
Oct 21 01:36:15 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:36:15 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
Oct 21 01:38:22 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:38:22 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
Oct 21 01:40:26 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:40:26 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
Oct 21 01:43:07 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:43:07 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
dpkg: error processing package collectd (--configure):
 installed collectd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 collectd
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've tried so many ways fo getting the package working including re-install all the dependencies:
https://askubuntu.com/questions/275719/reinstall-package-and-its-installed-dependencies

I'm having the same issue after upgrading to 24.04 and 8.0.3

r00buntu@r00buntu-server:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
r00buntu@r00buntu-server:~$ mysql --version
mysql Ver 8.0.39-0ubuntu0.24.04.2 for Linux on x86_64 ((Ubuntu))

running the "ALTER TABLE" command above results in
"ERROR 1046 (3D000): No database selected"

Collectd seems to be failing to install properly and this happens when running the troubleshooter:
2024-10-21T01:41:43 ==> start: Configuring collectd
A dependency job for collectd.service failed. See 'journalctl -xe' for details.

it seems... (pending successful update) i've fixed this by manually installing systemd-resolved (indicated in error logs as missing) and then the update ran fine.

UPDATE: I haven't managed to get it working entirely yet - blank dashboard now... collectd issues...

Any indication it'd be important to keep/uninstall systemd-resolved after?

My upgrade log:

Oct 20 23:39:16 box:taskworker Starting task 5817. Logs are at /home/yellowtent/platformdata/logs/tasks/5817.log
Oct 20 23:39:16 box:tasks update 5817: {"percent":1,"message":"Checking disk space"}
Oct 20 23:39:16 box:shell file execArgs: df ["-B1","--output=source,fstype,size,used,avail,pcent,target","/"]
Oct 20 23:39:16 box:tasks update 5817: {"percent":5,"message":"Downloading and verifying release"}
Oct 20 23:39:16 box:shell downloadUrl execArgs: curl ["-s","--fail","https://releases.cloudron.io/versions.json","-o","/home/yellowtent/platformdata/update/versions.json"]
Oct 20 23:39:16 box:updater downloadUrl: downloading https://releases.cloudron.io/versions.json to /home/yellowtent/platformdata/update/versions.json
Oct 20 23:39:16 box:updater downloadUrl: done
Oct 20 23:39:16 box:shell downloadUrl execArgs: curl ["-s","--fail","https://releases.cloudron.io/versions.json.sig","-o","/home/yellowtent/platformdata/update/versions.json.sig"]
Oct 20 23:39:16 box:updater downloadUrl: downloading https://releases.cloudron.io/versions.json.sig to /home/yellowtent/platformdata/update/versions.json.sig
Oct 20 23:39:16 box:updater downloadUrl: done
Oct 20 23:39:16 box:shell gpgVerify execArgs: /usr/bin/gpg ["--status-fd","1","--no-default-keyring","--keyring","/home/yellowtent/box/src/releases.gpg","--verify","/home/yellowtent/platformdata/update/versions.json.sig","/home/yellowtent/platformdata/update/versions.json"]
Oct 20 23:39:16 box:updater gpgVerify: /usr/bin/gpg --status-fd 1 --no-default-keyring --keyring /home/yellowtent/box/src/releases.gpg --verify /home/yellowtent/platformdata/update/versions.json.sig /home/yellowtent/platformdata/update/versions.json
Oct 20 23:39:16 box:shell downloadUrl execArgs: curl ["-s","--fail","https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz","-o","/home/yellowtent/platformdata/update/box.tar.gz"]
Oct 20 23:39:16 box:updater downloadUrl: downloading https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz to /home/yellowtent/platformdata/update/box.tar.gz
Oct 20 23:39:19 box:updater downloadUrl: done
Oct 20 23:39:19 box:shell downloadUrl execArgs: curl ["-s","--fail","https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz.sig","-o","/home/yellowtent/platformdata/update/box.tar.gz.sig"]
Oct 20 23:39:19 box:updater downloadUrl: downloading https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz.sig to /home/yellowtent/platformdata/update/box.tar.gz.sig
Oct 20 23:39:19 box:updater downloadUrl: done
Oct 20 23:39:19 box:shell gpgVerify execArgs: /usr/bin/gpg ["--status-fd","1","--no-default-keyring","--keyring","/home/yellowtent/box/src/releases.gpg","--verify","/home/yellowtent/platformdata/update/box.tar.gz.sig","/home/yellowtent/platformdata/update/box.tar.gz"]
Oct 20 23:39:19 box:updater gpgVerify: /usr/bin/gpg --status-fd 1 --no-default-keyring --keyring /home/yellowtent/box/src/releases.gpg --verify /home/yellowtent/platformdata/update/box.tar.gz.sig /home/yellowtent/platformdata/update/box.tar.gz
Oct 20 23:39:19 box:shell extractTarball execArgs: tar ["-zxf","/home/yellowtent/platformdata/update/box.tar.gz","-C","/tmp/box-450620418"]
Oct 20 23:39:19 box:updater extractTarball: extracting /home/yellowtent/platformdata/update/box.tar.gz to /tmp/box-450620418
Oct 20 23:39:20 box:updater extractTarball: extracted
Oct 20 23:39:20 box:updater Updating box with https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz
Oct 20 23:39:20 box:tasks update 5817: {"percent":70,"message":"Installing update"}
Oct 20 23:39:20 box:shell update /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-450620418 /home/yellowtent/platformdata/logs/tasks/5817.log
Oct 20 23:39:21 ==> installer: Updating from 7.7.2 to 8.0.3
Oct 20 23:39:21 ==> installer: Making sure apt is in a good state
Oct 20 23:39:21 ==> installer: Waiting for all dpkg tasks to finish...
[no timestamp] 
[no timestamp]  apt does not have a stable CLI interface. Use with caution in scripts.
[no timestamp] 
Jan 01 00:00:00 http://us.archive.ubuntu.com/ubuntu noble InRelease
Feb 01 00:00:00 https://linux.teamviewer.com/deb stable InRelease
Mar 01 00:00:00 http://us.archive.ubuntu.com/ubuntu noble-updates InRelease
Apr 01 00:00:00 http://security.ubuntu.com/ubuntu noble-security InRelease
May 01 00:00:00 http://us.archive.ubuntu.com/ubuntu noble-backports InRelease
Jun 01 00:00:00 https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu jammy InRelease [2,957 B]
[no timestamp]  2,957 B in 1s (4,211 B/s)
[no timestamp] 
[no timestamp] 
[no timestamp] 
Jan 01 00:00:00 packages can be upgraded. Run 'apt list --upgradable' to see them.
Oct 20 23:39:26 ==> installer: apt is ready
Oct 20 23:39:26 ==> installer: disabling unbound
[no timestamp]  state of unbound.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
[no timestamp]  /usr/lib/systemd/systemd-sysv-install disable unbound
Oct 20 23:39:29 ==> installer: enabling systemd-resolved
[no timestamp]  to enable unit: Unit file systemd-resolved.service does not exist.
Oct 20 23:39:31 box:shell update: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-450620418 /home/yellowtent/platformdata/logs/tasks/5817.log errored BoxError: update exited with code 1 signal null
[no timestamp]  at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:110:19)
[no timestamp]  at ChildProcess.emit (node:events:513:28)
[no timestamp]  at ChildProcess._handle.onexit (node:internal/child_process:291:12) {
[no timestamp]  reason: 'Shell Error',
[no timestamp]  details: {},
[no timestamp]  code: 1,
[no timestamp]  signal: null
[no timestamp]  }
Oct 20 23:39:31 box:taskworker Task took 14.695 seconds
Oct 20 23:39:31 box:tasks setCompleted - 5817: {"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:110:19)\n at ChildProcess.emit (node:events:513:28)\n at ChildProcess._handle.onexit (node:internal/child_process:291:12)","name":"BoxError","reason":"Shell Error","details":{},"message":"update exited with code 1 signal null","code":1,"signal":null}}
Oct 20 23:39:31 box:tasks update 5817: {"percent":100,"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:110:19)\n at ChildProcess.emit (node:events:513:28)\n at ChildProcess._handle.onexit (node:internal/child_process:291:12)","name":"BoxError","reason":"Shell Error","details":{},"message":"update exited with code 1 signal null","code":1,"signal":null}}
[no timestamp]  update exited with code 1 signal null
[no timestamp]  at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:110:19)
[no timestamp]  at ChildProcess.emit (node:events:513:28)
[no timestamp]  at ChildProcess._handle.onexit (node:internal/child_process:291:12)

I accidentally upgraded to 24.04 before properly upgrading to 8.+ hopefully this can be resolved without too much trouble?

I can't seem to edit members of my organization for some reason. There are some errors in the job, I'll pass them in.

Is the current version in cloudron the latest?