Cloudron Forum

Hey, thanks. Unfortunately not -sorry- as this is 100% vibe-coded (by a noob;-) and lots of things are hard coded. But maybe it's an idea for someone who knows what he/she does.

at first I found this in the logs
IMG_1052.heic: bad seek to 3140980
heif: Decoder plugin generated an error: Unspecified (7.0)
Send you an image via pm. mail to support@

Unfortunately it's still not working

Same problem again with the new package.

@Teiluj any plans to implement this in cloudron - as there is DeSec already as a domain provider. @girish @James

The idea of having to restore a Cloudron backup in an emergency has always stressed me out a bit. So, I spent some time "vibecoding" (...) and built a small Cloudron restore assistant. It knows all my Cloudron instances and backup storages. You can select the backup locations and specific backups via dropdown menus.
I just ran two test restores on fresh servers—worked like a charm. Sleeping a bit easier now.

Hey,
as netcup's dnssec is still a mess I'm thinking about moving the DNS part (not the domains themselves) to deSEC (offering API as well).
Is it possible in cloudron to change the dns provider of an existing domain on the fly? meaning: i change the provider and API and cloudron automatically creates all the entries with my new DNS provider?

omg.thanks - I really thought I did that...
working now

Hi,
after upgrading to Ubuntu 26.04 one of my instances can't backup anymore (EXT4, SSHFS). Creating a new backup storage ends in the same problem, Backups break up immediately:

Task 6987
Anzeige löschen
Vollständige Logfiles herunterladen
Sep 20 08:08:43 taskworker: Starting task 6987. Logs are at /home/yellowtent/platformdata/logs/tasks/6987.log
Sep 20 08:08:43 (node:69325) ExperimentalWarning: The supports Web Crypto API method is an experimental feature and might change at any time
Sep 20 08:08:43 (Use `node --trace-warnings ...` to show where the warning was created)
Sep 20 08:08:43 (node:69325) ExperimentalWarning: The ML-DSA-44 Web Crypto API algorithm is an experimental feature and might change at any time
Sep 20 08:08:43 taskworker: Running task of type backup
Sep 20 08:08:43 tasks: updating task 6987 with: {"percent":3.272727272727273,"message":"Backing up myapp.example.com (1/41). Waiting for lock"}
Sep 20 08:08:43 locks: write: current locks: {"full_backup_task_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx":null,"app_backup_yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy":"6987"}
Sep 20 08:08:43 locks: acquire: app_backup_yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy
Sep 20 08:08:43 tasks: updating task 6987 with: {"percent":3.272727272727273,"message":"Snapshotting app myapp.example.com"}
Sep 20 08:08:43 services: backupAddons: backing up ["localstorage","oidc"]
Sep 20 08:08:43 backuptask: snapshotApp: myapp.example.com took 0.002 seconds
Sep 20 08:08:43 tasks: updating task 6987 with: {"percent":3.272727272727273,"message":"Uploading app snapshot myapp.example.com"}
Sep 20 08:08:43 shell: backuptask: /usr/bin/sudo --non-interactive -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/app_yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx {"localRoot":"/home/yellowtent/appsdata/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy","layout":[]}
Sep 20 08:08:43 'close-from' does not take any arguments
Sep 20 08:08:43 usage: sudo -h | -K | -k | -V
Sep 20 08:08:43 usage: sudo [-ABbknS] [-p prompt] [-D directory] [-g group] [-u user] [-i | -s] [command [arg ...]]
Sep 20 08:08:43 usage: sudo -v [-ABknS] [-p prompt] [-g group] [-u user]
Sep 20 08:08:43 usage: sudo -l [-ABknS] [-p prompt] [-U user] [-g group] [-u user] [command [arg ...]]
Sep 20 08:08:43 usage: sudo -e [-ABknS] [-p prompt] [-D directory] [-g group] [-u user] file ...
Sep 20 08:08:43 shell: backuptask: /usr/bin/sudo --non-interactive -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/app_yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx {"localRoot":"/home/yellowtent/appsdata/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy","layout":[]} errored with code 1 and signal null timeout false terminated false - stdout: "" - stderr: ""
Sep 20 08:08:43 backuptask: runBackupUpload: backuptask crashed BoxError: /usr/bin/sudo exited with code 1 signal null
    at ChildProcess.<anonymous> (file:///home/yellowtent/box/src/shell.js:70:23)
    at ChildProcess.emit (node:events:509:28)
    at maybeClose (node:internal/child_process:1141:16)
    at Socket.<anonymous> (node:internal/child_process:498:11)
    at Socket.emit (node:events:509:28)
    at Pipe.<anonymous> (node:net:355:12) {
  reason: 'Shell Error',
  extra: {},
  stdout: '',
  stdoutString: '',
  stdoutLineCount: 0,
  stderr: '',
  stderrString: '',
  stderrLineCount: 0,
  code: 1,
  signal: null,
  timedOut: false,
  terminated: false
}
Sep 20 08:08:43 backuptask: fullBackup: app myapp.example.com backup finished. Took 0.013 seconds
Sep 20 08:08:43 locks: write: current locks: {"full_backup_task_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx":null}
Sep 20 08:08:43 locks: release: app_backup_yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy
Sep 20 08:08:43 tasks: setCompleted - 6987: {"result":null,"error":{"message":"Backuptask crashed","reason":"Internal Error","stack":"BoxError: Backuptask crashed\n    at runBackupUpload (file:///home/yellowtent/box/src/backuptask.js:190:15)\n    at async uploadAppSnapshot (file:///home/yellowtent/box/src/backuptask.js:359:34)\n    at async backupAppWithTag (file:///home/yellowtent/box/src/backuptask.js:382:26)"},"percent":100}
Sep 20 08:08:43 tasks: updating task 6987 with: {"completed":true,"result":null,"error":{"message":"Backuptask crashed","reason":"Internal Error","stack":"BoxError: Backuptask crashed\n    at runBackupUpload (file:///home/yellowtent/box/src/backuptask.js:190:15)\n    at async uploadAppSnapshot (file:///home/yellowtent/box/src/backuptask.js:359:34)\n    at async backupAppWithTag (file:///home/yellowtent/box/src/backuptask.js:382:26)"},"percent":100}
Sep 20 08:08:43 taskworker: Task took 0.068 seconds
Sep 20 08:08:43 BoxError: Backuptask crashed
    at runBackupUpload (file:///home/yellowtent/box/src/backuptask.js:190:15)
    at async uploadAppSnapshot (file:///home/yellowtent/box/src/backuptask.js:359:34)
    at async backupAppWithTag (file:///home/yellowtent/box/src/backuptask.js:382:26)
Sep 20 08:08:43 Exiting with code 0

hi @girish just split the forwarding adresses. A mail with 20 and then 28 addresses is being sent without problem. as soon as it take all the 48 its doesn't work anymore.

After updating to Cloudron 10.x, my mailing lists stopped working properly.

The main mailbox exists, and the forwarding addresses (48 recipients) are configured correctly. However, incoming emails are only delivered to the main Cloudron mailbox and are not being distributed/forwarded to the list members.

Interestingly, a newly created test mailing list works fine (though it only has 2 recipients configured). I also tried recreating the original list from scratch and re-pasting the addresses, but that didn't work either. The list is not restricted to list members only.

Regards,
Sponch

edit: tried smtp-relay (brevo) and built-in smtp Server

hi @timconsidine, thanks. I've already got that extra VPS with proxy running - just could save some bugs a month if could replace it with a cloudron version of netbird

Ah. No, thinking about the Reverse Proxy. (Custom public domains pointing to a Netbird device). The proxy is a non default opition during installation and can be also installed afterwards manually. You can find it in Dashboard under Reverse Proxy -> Custer
If not instaded

Sounds great. Is the Reverse Proxy working „out of the box“ this way? (By adding custom Domains)

@timconsidine should it not be
netbird up --management-url https://netbird.xxx.tld --setup-key xxx

@marcusquinn hey, its working now thanks! Do you think it's possible to include the proxy cluster in the installation? it's quite a pain to install that afterwards

@marcusquinn still not working here.
No possibility to create an account via Dashboard on initial start. Also had to change stun port because default is already in use here.

@girish yes, working now!

@girish sagte:

systemctl restart box

apply means: delete the "red marked" lines and insert the green?
Doesnt seem to work here.

Do you have any ideas for my mail problem?