T
Here's what I got back from the mysql command:
+------------------------------------------------+
| name |
+------------------------------------------------+
| /20250307100449-tokens-add-allowedIpRangesJson |
+------------------------------------------------+
@joseph I ran the script. The migration failed. Here's the output I got back:
1 updates could not be installed automatically. For more details,
see /var/log/unattended-upgrades/unattended-upgrades.log
Last login: Mon Nov 24 03:29:56 2025 from 73.245.168.195
root@wisdom:~# bash /home/yellowtent/box/setup/start.sh
2025-11-24T12:59:37 ==> start: Cloudron Start
media:x:500:
2025-11-24T12:59:38 ==> start: Configuring docker
Synchronizing state of apparmor.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable apparmor
2025-11-24T12:59:40 ==> start: Ensuring directories
2025-11-24T12:59:40 ==> start: Configuring journald
2025-11-24T12:59:41 ==> start: Setting up unbound
2025-11-24T12:59:41 ==> start: Adding systemd services
Synchronizing state of unbound.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable unbound
Synchronizing state of cron.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable cron
Synchronizing state of rpcbind.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable rpcbind
2025-11-24T12:59:52 ==> start: Configuring sudoers
2025-11-24T12:59:52 ==> start: Unconfiguring collectd
Synchronizing state of collectd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable collectd
2025-11-24T12:59:55 ==> start: Configuring logrotate
2025-11-24T12:59:55 ==> start: Adding motd message for admins
2025-11-24T12:59:55 ==> start: Configuring nginx
2025-11-24T12:59:55 ==> start: Starting mysql
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-24T12:59:56 ==> start: Migrating data
[ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: Data too long for column 'password' at row 1
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)
2025-11-24T12:59:57 ==> start: DB migration failed
Note: I made a light edit, changing app name to "[this_cloudron.app]"
@nebulon @girish I got to the logs from the terminal.
2025-11-24T03:35:08.728Z box:server ==========================================
2025-11-24T03:35:08.731Z box:server Cloudron 9.0.11
2025-11-24T03:35:08.731Z box:server ==========================================
2025-11-24T03:35:08.731Z box:platform initialize: start platform
2025-11-24T03:35:08.733Z box:tasks stopAllTasks: 0 tasks are running. sending abort signal
2025-11-24T03:35:08.733Z box:shell tasks: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/stoptask.sh all
2025-11-24T03:35:08.803Z box:locks releaseAll: all locks released
2025-11-24T03:35:08.808Z box:reverseproxy writeDashboardConfig: writing dashboard config for [this_cloudron.app]
2025-11-24T03:35:08.821Z box:shell reverseproxy: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/restartservice.sh nginx
2025-11-24T03:35:09.352Z box:updater notifyBoxUpdate: update finished from 8.3.2 to 9.0.11
2025-11-24T03:35:09.353Z Error starting servers
2025-11-24T03:35:09.353Z BoxError: Unknown column 'pending' in 'field list'
2025-11-24T03:35:09.353Z at Object.query (/home/yellowtent/box/src/database.js:96:22)
2025-11-24T03:35:09.353Z at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-11-24T03:35:09.353Z at async list (/home/yellowtent/box/src/tasks.js:163:21)
2025-11-24T03:35:09.353Z at async Object.setCompletedByType (/home/yellowtent/box/src/tasks.js:172:21)
My cloudron dashboard app (https://my.cloudron.app/) is down or unreachable. LDAP server is also down (can't login to some apps). However, other cloudron apps seem to be working. (Ghost blog is still getting served.)
The dashboard page shows:
"This app is currently not responding. Please try refreshing the page in a few minutes."
Previously, it showed some other sort of error (but I did not capture the message). I've attempted restarting the server with the same result.
I'm hosting on Vultr using the Cloudron Vultr server.
Not sure which cloudron version I'm on since I can't get to the dashboard. But previously updates were happening regularly I believe.
This is awful. Nextcloud calendar has become (effectively) unusable. Has anyone found a workaround? @nebulon were you able to figure out why you could not reproduce? Perhaps that's a potential workaround....
@girish 
it seems the most recent update worked....while i did change some email settings, the only other action I took was manually bumping along the updates several versions. So there must have been some sort of inconsistent state that came up.
It seems all is well with the world and no way to track down what happened.
Thanks for the help, all.
@girish I'm pretty sure i checked and there wasn't. I'll check again after the next scheduled automatic update and report back here to see if I see anything that points to an issue.
I've just re-installed Ghost to make this a non-blocking issue (and went through the brief hassle of re-importing content and configuration.) So this is a non-issue for me now.
@girish changing the update schedule didn't make a difference since updates were scheduled before, they just weren't being executed. So now they just fail to execute more frequently.
@girish
backups are working.
Cloudron platform version: v7.3.6 (Ubuntu 20.04.1 LTS)
Ghost package version: org.ghost.cloudronapp2@4.6.0
I hadn't used my Ghost install for a while. Automatic updates have been on the entire time:
However, it seems updates have not been happening. It's currently at 5.5 where 5.37 is the latest. So manually moving forward 1 step each time is not desirable.
2 questions:
( Possible answer: I have not updated my cloudron for a while.....which is another issue i need to address.....cough cough...SSH keys lost)
I was unable to find any official documentation showing a breaking API change. However I did find this python library that seemed to be on top of its game: Citric. 
Their "save_responses"/"export_responses" method still worked, so as a temporary measure I was able to drop in their method to get data flow working again.
I haven't dug into their code further yet to see what specifically changed/broke, but I'm going to mark this thread as resolved (before I lose it), as someone can read that code to find the specific solution if needed.
@girish Thanks for chiming in on this promptly. There were no errors in the logs (just showed a 500 response returned.)
Was able to get this resolved, see below.
@nebulon Based on my time-limited search, wasn't able to find a way to submit an issue that seemed viable. Limesurvey github project has issues deactivated. Quickly checked site, have forum, but decided not to mess with it.
Was able to find a fix though.....see below
The upgrade from Cloudron Limesurvey release 1.34.11 to 1.34.12 broke the "export_responses" API call (throws a 500 error).
Nothing related to api listed in change log for this release:
Changes from 5.4.12 (build 221121) to 5.4.13 (build 221128) November 28, 2022
-Fixed issue: gid suffix was missing in aRDP_regexpStaticAttribute array (Tim Willig)
-Fixed issue #18463: List of uploaded files should be sorted alphabetically (#2722) (Gabriel Jenik)
-Fixed issue #18461: Survey groups at survey list screen should be listed alphabetically (#2724) (Gabriel Jenik)
-Fixed issue #18424: Typo in debug message (#2705) (Gabriel Jenik)
-Fixed issue #18395: Access to limereplacementfields didn't check read permission on survey (#2655) (Gabriel Jenik)
-Fixed issue #17648: Email received by participant is empty (#2691) (Denis Chenu)
#Updated translation: Portuguese (Brazil) by rafaelmaia
#Updated translation: Polish by elissa
#Updated translation: Polish (Informal) by elissa
#Updated translation: Luxembourgish by Mazi
#Updated translation: Italian by lfanfoni
#Updated translation: Italian (Informal) by lfanfoni
#Updated translation: German by c_schmitz
#Updated translation: German (Informal) by c_schmitz
#Updated translation: French (France) by b00z00, DenisChenu, Nickko, sim.eesp
#Updated translation: Dutch by Han
#Updated translation: Dutch (Informal) by Han
#Updated translation: Chinese (Simplified) by hdaphq, humandynamic, xiongrui, zengqing, zhanginshanghai, Zoctan
#Updated translation: Azerbaijani by Heyder
Reporting here in case this is a cloudron specific issue -- there are some more recent releases of limesurvey that don't mention any issues being noted yet in the changelog.
Will also check with LimeSurvey directly to see what I find.
This is a critical issue for me that interrupts service. However, I was able to roll back to the prior release as a temporary fix that seems to only have created data migration headaches.
Would appreciate any intel that anyone finds related to this issue.
Also, for those that don't know what HLS is (I didn't prior to running into this issue), here's a link to get you started with "HTTP Live Streaming":
**Adaptability **
To enable a player to adapt to the bandwidth of the network, the original video is encoded in several distinct quality levels. The server serves an index, called a "master playlist", of these encodings, called "variant streams". The player can then choose between the variant streams during playback, changing back and forth seamlessly as network conditions change.
https://en.wikipedia.org/wiki/HTTP_Live_Streaming#Adaptability
Just a quick update from me....
I did an initial test using cal.com (hosted by them) and their CalDAV integration with NextCloud, and it failed some of my required use case tests (recurring invites were buggy.....although it looks like one of the use cases may have been fixed already, so this means progress is being made....and I may need to re-test soon).
So this isn't quite high enough priority for me to mess with getting the deployment on Cloudron figured out since it can't quite solve my use case yet....
However, if you want this to progress, here's what I suggest:
post issues and talk back to the cal.com team.
The Cal team has a CalDAV integration issues roundup here you can check, comment on, prior to posting additional issues that you run into: https://github.com/calcom/cal.com/issues/3457
@subven thanks a lot for helping us get to the bottom of this.
The webtorrent selection UI in the settings is a bit odd (and the peertube documentation has no search functionality), so your writeup should hopefully help any future travelers figure it out.
I was able to find the the relevant section in the Peertube Docs now that explains these options a bit. HLS is actually the recommended setting by them as well:
We recommend you to enable HLS (and disable WebTorrent if you don't want to store 2 different versions of the same video resolution) because video playback is really better
https://docs.joinpeertube.org/admin-configuration?id=webtorrent-transcoding-or-hls-transcoding