Perfect. Everything works as intended.

Thank you, @girish, and have a great beginning of your week

Hey @girish, thanks for fix.

Just as @thoschworks, I got a "Copy of Default" backup destination, which I intend to use from now on. I haven't tried to execute a backup yet.

Upgrade to 9.0.10 fails partially

Hello,

So I have tried to upgrade from 8.3.2 to 9.0.10. At some point the dashboard would freeze indefinitely. The log indicates a DB migration failed.

But when I reboot the VM, everything seems to be working fine, at least until a try to execute a backup, which will fails, presumably because the DB migration failed.

Any help would be appreciated. (I have a paid subscription, but I figured it would be more helpful to other users If I share info here instead of using email support).

Backup logs:

Nov 16 01:01:46 box:locks write: current locks: {"full_backup_task_3c8364e2-f2b2-4a1c-84c8-d5bd386016f4":null}
Nov 16 01:01:46 box:locks release: app_backup_04439498-8ce4-48b2-9b09-dc8492c571f7
Nov 16 01:01:46 box:tasks setCompleted - 17471: {"result":null,"error":{"message":"Unknown column 'siteId' in 'field list'","reason":"Database Error"},"percent":100}
Nov 16 01:01:46 box:tasks updating task 17471 with: {"completed":true,"result":null,"error":{"message":"Unknown column 'siteId' in 'field list'","reason":"Database Error"},"percent":100}
Nov 16 01:01:46 box:taskworker Task took 105.083 seconds
Nov 16 01:01:46 BoxError: Unknown column 'siteId' in 'field list'
Nov 16 01:01:46 at Object.query (/home/yellowtent/box/src/database.js:96:22)
Nov 16 01:01:46 at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Nov 16 01:01:46 Exiting with code 0

Update logs:

I could not find the update logs, but the error message here is similar when I execute the following

sudo /home/yellowtent/box/setup/start.sh

mysqladmin: [Warning] Using a password on the command line interface can be insecure.
Warning: Since password will be sent to server in plain text, use ssl connection to ensure password safety.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
2025-11-16T09:25:55 ==> start: Migrating data
Backup counts. rsync: 1 tgz: 231 total: 232 . theOneFormat: null
Existing format is tgz . Adding clone backup site for rsync
[ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: Unknown column 'priority' in 'field list'
    at /home/yellowtent/box/node_modules/db-migrate/lib/commands/on-complete.js:15:14
    at tryCatcher (/home/yellowtent/box/node_modules/bluebird/js/release/util.js:16:23)
    at Promise.successAdapter (/home/yellowtent/box/node_modules/bluebird/js/release/nodeify.js:22:30)
    at Promise._settlePromise (/home/yellowtent/box/node_modules/bluebird/js/release/promise.js:601:21)
    at Promise._settlePromiseCtx (/home/yellowtent/box/node_modules/bluebird/js/release/promise.js:641:10)
    at _drainQueueStep (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:97:12)
    at _drainQueue (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:102:5)
    at Async.drainQueues [as _onImmediate] (/home/yellowtent/box/node_modules/bluebird/js/release/async.js:15:14)
    at process.processImmediate (node:internal/timers:485:21)
    at Packet.asError (/home/yellowtent/box/node_modules/mysql2/lib/packets/packet.js:740:17)
    at Query.execute (/home/yellowtent/box/node_modules/mysql2/lib/commands/command.js:29:26)
    at Connection.handlePacket (/home/yellowtent/box/node_modules/mysql2/lib/base/connection.js:477:34)
    at PacketParser.onPacket (/home/yellowtent/box/node_modules/mysql2/lib/base/connection.js:93:12)
    at PacketParser.executeStart (/home/yellowtent/box/node_modules/mysql2/lib/packet_parser.js:75:16)
    at Socket.<anonymous> (/home/yellowtent/box/node_modules/mysql2/lib/base/connection.js:100:25)
    at Socket.emit (node:events:519:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)

System Details

Cloudron Version

"version": "9.0.10"

Ubuntu Version

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 24.04.3 LTS
Release:	24.04
Codename:	noble

Cloudron installation method

Options:

• Manual with ./cloudron-setup

Output of cloudron-support --troubleshoot

sudo cloudron-support --troubleshoot
Vendor: QEMU Product: Standard PC (Q35 + ICH9, 2009)
Linux: 6.8.0-87-generic
Ubuntu: noble 24.04
Processor: 13th Gen Intel(R) Core(TM) i5-13400
BIOS pc-q35-10.1  CPU @ 2.0GHz x 4
RAM: 19976216KB
Disk: /dev/vda2       104G
[OK]	node version is correct
[OK]	IPv6 is enabled in kernel. No public IPv6 address
[OK]	docker is running
[OK]	docker version is correct
[OK]	MySQL is running
[OK]	nginx is running
[OK]	dashboard cert is valid
[OK]	dashboard is reachable via loopback
[OK]	box v9.0.10 is running
[OK]	netplan is good
[OK]	DNS is resolving via systemd-resolved
[OK]	Dashboard is reachable via domain name
[WARN]	Domain XXXXXX.ch e

Hello @nebulon, well spotted.

Thanks for pushing this fix. I have updated the app, and it is running fine now.

Some logs as well below.

So until ~19:34 this is the original configuration.

Then I did reboot to emergency mode, fixed the brackets, and then rebooted.

When I reboot the container and it works, which prisma correctly prints the path. If the host is rebooted, then it fails again (as the fix / workaround is, as expected, not retained)

I assume that adding the brackets would have no adverse effects.

Oct 27 19:34:15 /app/pkg/start.sh: line 54: prisma: command not found
Oct 27 19:34:15 => Setting up OIDC
Oct 27 19:34:15 => Updating permissions
Oct 27 19:34:15 => prisma migrate
Oct 27 19:35:12 Repair mode. Use the webterminal or cloudron exec to repair. Sleeping
Oct 27 19:37:55 => Setting up OIDC
Oct 27 19:37:55 => Updating permissions
Oct 27 19:37:55 => prisma migrate
Oct 27 19:37:58 2025-10-27T19:37:58+01:00
Oct 27 19:37:58 2025-10-27T19:37:58+01:00
Oct 27 19:37:58 2025-10-27T19:37:58+01:00
Oct 27 19:37:58 > Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 0%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 1%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 3%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 4%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 6%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 7%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 8%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 11%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 16%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 20%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 22%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 25%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 27%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 28%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 31%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 33%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 35%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 37%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 39%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 43%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 46%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 48%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 50%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 55%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 60%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 64%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 69%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 73%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 78%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 82%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 88%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 91%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 93%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 95%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 97%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 98%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 100%Environment variables loaded from .env
Oct 27 19:37:58 Datasource "db": PostgreSQL database "dbe49f54e745c046d38f7e4a0e61387c84", schema "public" at "postgresql:5432"
Oct 27 19:37:58 Prisma schema loaded from ../../../pkg/prisma/schema.prisma
Oct 27 19:37:58 No pending migrations to apply.
Oct 27 19:37:58 96 migrations found in prisma/migrations
Oct 27 19:37:58 => Starting Rallly
Oct 27 19:37:59 2025-10-27T19:37:59+01:00
Oct 27 19:37:59 ▲ Next.js 15.4.6
Oct 27 19:37:59 ✓ Ready in 430ms
Oct 27 19:37:59 ✓ Starting...
Oct 27 19:37:59 - Local: http://e49f54e7-45c0-46d3-8f7e-4a0e61387c84:3000
Oct 27 19:37:59 - Network: http://e49f54e7-45c0-46d3-8f7e-4a0e61387c84:3000

Hello, same error here.

I did reinstall the application once, from scratch. At first, it did work, until it did not.

@andreasdueren suggested fix worked for me. Thank you.

@joseph that was indeed correct. I just generated another token, and it is now working correctly.

There was an issue with the Gandi dashboard yesterday. Did not take the time to properly troubleshoot it. Looks like it indeed was a problem on the Gandi side of things.

Thanks for your help.

Side note: I love your product, and I have been happy paying subscriber for the past few years now. Keep up with the good work

@jdaviescoates

Yes, I have. It is when I do so that I get the error:

Configuration error: Gandi DNS error [500] The server has either erred or is incapable of performing the requested operation.

Hello @girish !

On Cloudron v8.2.4 and an existing installation, I can select the Personal Access Token (PAT) but it does not refresh the box below (see screenshot). So I cannot provide a newly generated PAT.

Tried on latest version of Firefox and Chromium.

I haven't found a workaround.

I get that error when I provide a correctly scoped PAT:

Configuration error: Gandi DNS error [500] The server has either erred or is incapable of performing the requested operation.

Any help is appreciated (I assume a bug fix might is required).