Cloudron Forum

A tweak (mostly UI) that would let me say “run all missing updates one after another”, would save a lot of waiting and clicking for those cases where a version of cloudron or some app was held back.

Described here and here.

@necrevistonnezr said:

What’s the VPS?

One from Greenhost. No idea why it would differ from the default then, in this regard. If pretty much every other Ubuntu installation does have wget (which I’d hope) then indeed it seems fine to ignore this (non-)issue, I might better raise it at the hoster instead.

For the record, their VPS also had another customisation that conflicted with Cloudron: by default the VPS kernel is managed outside the VPS, and /lib/modules is a tmpfs filesystem prefilled with defaults and automatically populated on each boot. Cloudron tries to install/update some kernel-related packages, which complaints about ‘no space left on device’. (I reinstalled the VPS with a ‘stock kernel’ option, which did not pose this problem.)

Hi, this drop-in replacement for Github Pages works great.

Looking at the source code, it looks like the pages are served directly by the Express framework in NodeJS; correct? I wonder how well this performs under load; any estimates/experiences? (we are considering hosting redecentralize.org on our own server, but are a little worried about e.g. a slashdot effect taking it down when it is needed most..)

The Express docs suggest running e.g. nginx as a cache in front of it, might that be a good idea? And if not, perhaps at least the app could use gzip compression?

(besides, using an nginx server might also be useful to e.g. obtain server logs for statistics, but that’s a separate question)

The Cloudron installation instructions say:

Create a fresh Ubuntu Noble 24.04 x64 server and run these commands

wget https://cloudron.io/cloudron-setup
chmod +x ./cloudron-setup
./cloudron-setup

However my fresh ubuntu server answers:
-bash: wget: command not found

It’s easily fixed by first running apt install wget, but I imagine that for some of cloudron’s target audience this might be a showstopper.

(Note I’m not sure if the Ubuntu my VPS provider offers is less equipped than other people’s Ubuntu..)

And another piece of feedback on installation experience: while installing, I lost my internet connection for a bit, so ssh dropped. Not sure if it’s related, but the installation appears to be half-completed and I don’t know how to continue.

The last messages on my screen (IP address redacted):

=> Checking version
=> Downloading Cloudron version 8.0.6 ...
=> Installing base dependencies (this takes some time) ...Timeout, server 123.123.123.123 not responding.

Last lines of /var/log/cloudron-setup.log:

Importing restoreConfigs
[INFO] Processed migration 20170418073650-backups-add-restoreConfigJson
[INFO] Processed migration 20170423032116-settings-set-default-retentionSecs
[INFO] Processed migration 20170628173051-settings-default-mailrelay

My login prompt does tell me:

Visit one of the following URLs and accept the self-signed certificate to finish setup.

• https://123.123.123.123

But that page does not load. (with insecure http it does give an nginx page though.)

If I rerun the setup I get little help:

Error: Cloudron is already installed. To reinstall, start afresh

Perhaps installation is indeed completed? If so I would have expected a success message at the end of the log file. (But the https server appears not to work, so I still guess something went wrong.)

PS Indeed it worked fine when reinstalling the OS, and redoing the installation steps. Though I hope some day there will be a quicker way to continue/restart the installation, and/or have it continue/pause when the shell is disconnected: Not everybody has the luxury of stable internet connectivity.

@girish done! https://forum.cloudron.io/topic/6333/update-to-latest-button-option

@girish said in Cloudron update failing:

Indeed, the docker install logic was not cleaned up properly when we cleaned up other package installs. fixed now - https://git.cloudron.io/cloudron/box/-/commit/09d3d258b61ba338c0fadc88c0418d8bcc77f528 . Thanks for investigating!

Perhaps that fixes a similar bug, but just for clarity, note that I was using an old version Cloudron (6.1.2), and got stuck in this other loop that looks like it has already been removed from the script between version 6.2 and 6.3.

while ! dpkg --force-confold --configure -a; do
    log "Failed to fix packages. Retry"
    sleep 1
done

That “Failed to fix packages” is the message that appeared again and again in my infinite logs:

2022-01-13T17:05:53 ==> installer: Updating from 6.1.2 to 6.2.7
2022-01-13T17:05:53 ==> installer: updating docker
2022-01-13T17:05:58 ==> installer: Waiting for all dpkg tasks to finish...
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-modules-extra-5.4.0-59-generic; however:
  Package linux-modules-extra-5.4.0-59-generic is not installed.

dpkg: error processing package linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-image-generic (= 5.4.0.59.62); however:
  Package linux-image-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-5.4.0-59-generic:
 linux-image-5.4.0-59-generic depends on linux-modules-5.4.0-59-generic; however:
  Package linux-modules-5.4.0-59-generic is not installed.

dpkg: error processing package linux-image-5.4.0-59-generic (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-generic
 linux-generic
 linux-image-5.4.0-59-generic
2022-01-13T17:05:58 ==> installer: Failed to fix packages. Retry
dpkg: dependency problems prevent configuration of linux-image-generic:
…
…

For statistics, had the same issue here.

2023-02-08T13:57:54.944Z box:tasks setCompleted - 6496: {"result":null,"error":{"stack":"BoxError: Failed to download https://s3.amazonaws.com/prod-cloudron-releases/versions.json: downloadUrl exited with code 22 signal null\n    at /home/yellowtent/box/src/updater.js:50:26\n    at processTicksAndRejections (internal/process/task_queues.js:95:5)\n    at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)\n    at async downloadUrl (/home/yellowtent/box/src/updater.js:42:5)\n    at async downloadAndVerifyRelease (/home/yellowtent/box/src/updater.js:110:5)\n    at async update (/home/yellowtent/box/src/updater.js:145:25)","name":"BoxError","reason":"Network Error","details":{},"message":"Failed to download https://s3.amazonaws.com/prod-cloudron-releases/versions.json: downloadUrl exited with code 22 signal null"}}

I deleted /home/yellowtent/platformdata/update/updatechecker.json, and also versions.json.sig from the same folder (otherwise there was no ‘check versions’ button at all in the UI). Then systemctl restart box as described, seemed to work. (to then discover other update issues, but probably unrelated..)

Ok.. the underlying cause seems to have been that my /lib/modules is a 100MB tmpfs filesystem, on which dpkg tried to unpack 250MB of files. I don’t know how/why this happened, but I suppose it is not Cloudron’s fault either. (I managed to solve things by running umount /lib/modules so I could run apt --fix-broken install without the disk space error; I’m somewhat surprised the machine managed to reboot after that)

Anyhow, the part that is relevant for Cloudron seems to be that an issue in ubuntu/dpkg/whatever while updating things can apparently end up in an infinite loop that blocks future updates while creating gigabytes of log files; without feedback to the user that something is going wrong, let alone what is going wrong. Perhaps it could already help to have a time-limit on the updater service, and/or making dpkg stop rather than keep retrying, and then the UI can report that updating failed?