Cloudron Forum

@girish Here are the results. Still non-operable.

@girish I'm even more confused. To the best of my knowledge, I haven't messed with the Node version.

It's using /usr/bin/node, which oddly enough seems to be the only package not symlinked. The first command you gave me shows Node v20.18.0. The second command shows Node v12.22.9. The latter appears to be a default package included with Ubuntu 24.04.1 LTS.

Full Data:

Listing of /usr/bin, scoped to grep node

Listing of installed packages, scoped to grep node

@scooke Of course you're right. The only conclusion I can come up with is that simply adding the Docker PPA results in an apt update AND apt upgrade. The update is visible, but there's no indication it's running apt upgrade.

Node is more complicated. I'll double check, but I don't recall installing fnm or anything. I may have to reach out to Hostinger about these issues.

@girish Well that's interesting. I get Welcome to Node.js v12.22.9
Type ".help" for more information.

How in the world is that possible? How can I fix it?

Here's a screenshot showing the output of both cloudron-support --troubleshoot and node --version. Apologies for the attitude in the original post. Just frustrated.

I've been having odd issues with my Cloudron for the past week or so. Apps were running fine, but backup tasks were failing. It'd refer me to the logs, which when checked, stated the file had been moved or did not exist.

I'm set up to backup to S3 via rsync. It was working fine initially, so I'm not sure what happened. In any case, I created a snapshot (which supposedly saves state, and yet...) and made the boneheaded decision to reboot my VPS. It came back up, but I got the dreaded red "Cloudron is offline. Reconnecting..." banner. Something I've seen way too many times.

I attempted to restore via snapshot, still getting the banner. I'm honestly wondering if the Cloudron distribution that Hostinger uses is fully stable. This has to be my 3rd or 4th attempt. It'll work fine at first, but inevitably the ticking time bomb goes off, and all I get is a red banner for no good reason.

Cloudron-troubleshoot instructed me to run cloudron --fix-docker, as somehow Docker was a newer version. I've learned my lesson about running apt upgrade long ago, so I have no idea how that's possible. Would simply adding the PPA upgrade it as well?

Regardless, it appeared it was going to succeed, but when it tries to start box, it just keeps restarting. This leads to an output of [FAIL] box service keeps restarting, please investigate the error by inspecting /home/yellowtent/platformdata/logs/box.log. The box.log (and 1, 2, and 3) are massive, and I have no idea what I'm looking for.

Running journalctl -xeu box gave me the following:

░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit box.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Jan 10 06:37:24 c.example.com systemd[1]: box.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit box.service has entered the 'failed' state with result 'exit-code'.
Jan 10 06:37:24 c.example.com systemd[1]: box.service: Scheduled restart job, restart counter is at 2815.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ Automatic restarting of the unit box.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jan 10 06:37:24 c.example.com systemd[1]: Stopped Cloudron Admin.
░░ Subject: A stop job for unit box.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A stop job for unit box.service has finished.
░░ 
░░ The job identifier is 868014 and the job result is done.
Jan 10 06:37:24 c.example.com systemd[1]: Started Cloudron Admin.
░░ Subject: A start job for unit box.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit box.service has finished successfully.
░░ 
░░ The job identifier is 868014.
Jan 10 06:37:24 c.example.com box.js[514142]: /home/yellowtent/box/src/ldapserver.js:206
Jan 10 06:37:24 c.example.com box.js[514142]:         if (req.app.accessRestriction?.groups?.indexOf(group.id) === -1) continue;
Jan 10 06:37:24 c.example.com box.js[514142]:                                       ^
Jan 10 06:37:24 c.example.com box.js[514142]: SyntaxError: Unexpected token '.'
Jan 10 06:37:24 c.example.com box.js[514142]:     at wrapSafe (internal/modules/cjs/loader.js:915:16)
Jan 10 06:37:24 c.example.com box.js[514142]:     at Module._compile (internal/modules/cjs/loader.js:963:27)
Jan 10 06:37:24 c.example.com box.js[514142]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
Jan 10 06:37:24 c.example.com box.js[514142]:     at Module.load (internal/modules/cjs/loader.js:863:32)
Jan 10 06:37:24 c.example.com box.js[514142]:     at Function.Module._load (internal/modules/cjs/loader.js:708:14)
Jan 10 06:37:24 c.example.com box.js[514142]:     at Module.require (internal/modules/cjs/loader.js:887:19)
Jan 10 06:37:24 c.example.com box.js[514142]:     at require (internal/modules/cjs/helpers.js:85:18)
Jan 10 06:37:24 c.example.com box.js[514142]:     at Object.<anonymous> (/home/yellowtent/box/box.js:7:18)
Jan 10 06:37:24 c.example.com box.js[514142]:     at Module._compile (internal/modules/cjs/loader.js:999:30)
Jan 10 06:37:24 c.example.com box.js[514142]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
Jan 10 06:37:24 c.example.com systemd[1]: box.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit box.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Jan 10 06:37:24 c.example.com systemd[1]: box.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit box.service has entered the 'failed' state with result 'exit-code'.
Jan 10 06:37:24 c.example.com systemd[1]: box.service: Scheduled restart job, restart counter is at 2816.

SyntaxError: Unexpected token '.' appears to be the issue, but from what I've read the error only occurs in very old (<14) Node versions. Would really appreciate some assistance getting this up and running.

If I have to nuke this box again, I think I'll forego Cloudron and just use the dedicated Nextcloud image. Far more limiting than I'd like, but better than endless failures.

~ SunDevil ~

@nebulon Okay, that makes sense. I had assumed as much. With that being said, what's the proper procedure to upgrade PHP, or is that handled automatically by Cloudron?

Could someone confirm what version of Node and PHP we should be on and/or migrating to? I ask because I've had a significant amount of trouble with packages seemingly getting upgraded automatically. I'm aware of the need to upgrade PHP to at least 8.2 (within the Nextcloud container, anyway).

To be cautious, I disabled apt's Unattended Upgrade and Automatic Security Updates. As detailed in the Ubuntu documentation, it seems dependencies and whatnot are fair game if a security update requires it. That was before I realized this is more complex, as there's an isolated file system that runs within the Nextcloud Docker container.

I didn't see anything that would cause automatic updates as far as apt is concerned. My confusion partly stems from troubleshooting now-restored systems (thank goodness for "snapshots"). The cloudron-support --troubleshoot command appears to check the versions outside the container environment, while I couldn't get it to work at all inside the Nextcloud Docker shell.

That doesn't make much sense, so I'm assuming I'm doing something wrong there.

Currently, my "exterior" packages for node and PHP are v20.17.0 and 8.3.6, respectively. The container environment reports node @ v18.18.0 and PHP @ 8.1.2. I make sure not to upgrade packages, so I'm assuming these are the default versions for Ubuntu 24.04.

Is there a suggested method for updating PHP or just apt install php8.3* (within the container)?

Appreciate the help!

@msbt Thank you immensely! I've been trying to get that to work for ages.

@girish Absolutely! No problem, I'll shoot you guys an email at that address. Thank you!

Hi all,

Hoping someone can help me figure this out. I'm attempting to install my second app (Discourse), and I'd like to use a secondary domain that I added to Cloudron.

When I attempt to install the app on the secondary domain, Cloudron prompts me to purchase a subscription. However, it appears that it'll let me install on the primary domain.

The secondary is preferred, as it'd be a much shorter address. Is this expected behavior, and if so, what is the justification for restricting app installs to the primary domain only? One would think an app install is an app install, irrespective of domain used.

The only thing that jumps out at me is that only the primary domain is listed under my Cloudron Account. I don't see any way in which to edit or add to this.

Thanks in advance for any assistance you can lend!