Cloudron Forum

There were a bunch of dangling images. Deleted those. Update failed because you no longer use AWS (....lol), but after https://forum.cloudron.io/post/59939
Update is complete. Well, 5 or 10 updates. Hey, everything kept working for years...!

Surfer installed successfully. Thank you for your help!

Note to anyone doing this in the future: the updates will result in a lot of backups (which can be removed via the web interface or at /var/backups) and a bunch of dangling or unused docker images which can be removed with
docker system prune
or
docker system prune -a

HI!

I've got a script that generates an updated .ics calendar file for me every day. I have a website (Wordpress / Cloudron / my own domain).

I'd like to put the script on the same VPS as Cloudron and run it as a cron job. How should I do this? Where should I put the file such that the script can access it and update it without messing it up, AND it will be accessible via URL?

I just don't 100% understand how Cloudron works and I don't want to mess it up by tinkering with its insides

I could use Wordpress's Media Library feature to upload a single .ics, then ssh into the server, find it on disc, and have the script update it there...?

Pete

Updates have been failing because not enough disk space. Now time to see what can be eliminated...

Heyo,

I have a script I'm going to run on my Cloudron server, it updates a .ics file hosted with Surfer. I'd like to receive an email at my regular (non-Cloudron) account when the login credentials stop working or for some other reason the script updating the .ics file fails.

Is there a way I can send emails from the script while leaving Cloudron email in its stock state? The automated emails it sends right now work just fine. I'd prefer not to have to enable receiving, set up user accounts, etc. This thread is tangentially related but didn't hit the nail on the head: https://forum.cloudron.io/topic/3965/use-cloudron-email-for-sending-email-smtp-on-application-hosted-outside-cloudron

Thanks for your help

The script currently lives in the home directory of the VPS instance that hosts Cloudron, and it updates a file exposed to the world by Surfer. Ideally there is a line or two I can add to the script (python) that sends an email if the script fails. Obviously Cloudron has some built-in capabilities for this, since it sends emails; can I access these capabilities easily? I'd like to avoid having to install an email client, set up users, etc.

Hey all,

I'm seeing in /home/yellowtent/platformdata/logs/box.log:

2024-06-07T12:58:29.738Z box:platform BoxError: startMysql errored with code 125 message Command failed: docker run --restart=always -d --name=mysql                 --hostname mysql                 --net cloudron                 --net-alias mysql                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mysql                 --dns 172.38.some.IP                 --dns-search=.                 --ip 172.32.some.IP                 -e CLOUDRON_MYSQL_TOKEN=somestuff                 -e CLOUDRON_MYSQL_ROOT_HOST=172.18.0.1                 -e CLOUDRON_MYSQL_ROOT_PASSWORD=somestuff                 -v /home/yellowtent/platformdata/mysql:/var/lib/mysql                 --label isCloudronManaged=true                 --cap-add SYS_NICE                 --read-only -v /tmp -v /run registry.docker.com/cloudron/mysql:3.4.2@sha256:some_hash 
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/yellowtent/platformdata/mysql" to rootfs at "/var/lib/mysql": mount /home/yellowtent/platformdata/mysql:/var/lib/mysql (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.

    at /home/yellowtent/box/src/shell.js:71:23
    at ChildProcess.exithandler (node:child_process:427:5)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at ChildProcess._handle.onexit (node:internal/child_process:302:5)

When mysql starts after upgrading. This means a bunch of stuff doesn't work.

• I've tried upgrading from Ubuntu 20.04 to 22.04, that seemed to work but the problem persists.
• I've tried docker container prune and docker volume prune, restart, same problem.
• I've tried the mysql troubleshooting instructions here: https://docs.cloudron.io/troubleshooting/#mysql-addon

Any ideas? It seems like it's a permissions thing, but I don't want to tinker with Cloudron's guts too much.

@girish Thanks for checking in. I have not gotten it sorted out...if I revert to a previous Cloudron version everything is fine! Which leads me to believe something's going wrong with the upgrade.

Thank you @girish , this worked.

For those coming through in the future note that cloudron-support may ask you to reboot and run again, keep an eye out for it.