That's a fantastic idea! I will add it. I ended up migrating it off Cloudron for the time being because I have come to depend on UK for work and all the notifications were bogging me down.
I will restart the old instance to test and will report back what I find out.
Hey thanks for getting back! My TLD is .LA.
I know this is an old thread, but I'm also having this issue and curious if anyone has found a solution other than upping retries. Or perhaps there's another service similar to Uptime Kuma that doesn't have these issues?
I wish it was, but the DNS was already set to my new IP address for all of the instances on my Cloudron. I tried doing the restore multiple times, choosing enabling and disabling the dry run option as I tried to figure things out.
So- after a bit of fighting with it, I was able to get all of the containers online. Many failed, but eventually the interface became responsive and I was able to restore each individually.
I think one of the things that's happening is they'are all trying to restore simultaneously. Perhaps if it restored in a linear way, there would be a bit more stability.
Hi all,
I'm having a tough time migrating my server hosted on DigitalOcean over to my own Proxmox. I created an Ubuntu 22.04 VM with 12GB memory and 320GB storage. There are 12 containers (all pretty small) on my Cloudron instance that need to be restored. I have been backing up to filesystem (following the backup/restore guide in docs) and copying the files over to the new box (I made sure permissions in entire directory are owned by yellowtent:yellowtent). When I go through the restore process, the new instance becomes very unresponsive. When I access the web interface, I can see that it is trying to restore the containers, but many of them error out. If I try to click on one of the containers to see what is happening, it gives me an error saying the app isn't responding.
Not sure how to troubleshoot but happy to provide any logs.
Thanks!
@rmdes I ended up setting up a local backup for Cloudron and use RClone to handle the backup. I've used RClone for years with no issue, and since going this route, no issues with my Cloudron backup.
@girish Thank you for the pointer! I've spent a bit of time trying to convert my MBOX files using mb2md and it seems like there's some sort of bug that isn't working with my files.
I am getting the following error thousands of times:
Use of uninitialized value $t in utime at /usr/bin/mb2md line 1043, <MBOX> line 36621221
I will report back when I have a solution!
Hi all,
Please excuse me if this has been covered before (if so, would love a pointer!). I have a customer with lots of archived email boxes (originally PST & converted to MBOX format) and I was wondering if anyone has any tips on importing them into Cloudron email.
My goal is to have a web-based, easily searchable mailbox for each archived mail account. If it's possible to convert the MBOX files into something that works with Cloudron, my idea is to setup a subdomain dedicated to archived accounts, and create logins for each inbox (archiveduser1@archive.example.com).
Any help in achieving this is greatly appreciated!
Thanks!
@robi I was able to get it running reliably by mounting the path for the bridge and making some file permission changes for registration.yaml. Was super straightforward and works great!
@robi I'm new to Matrix but was curious if you have any guidance on how to set this up when using a Cloudron deployed Synapse server. I got the docker version running and generated the config files, but I don't know what path to put in the homeserver.yaml since it runs in it's own environment.
Just discovered this and it's awesome. They just updated and came out with a ton of new features! The dev says they are where they want to be with the server at this point, so fewer breaking changes. Might be worth another look for Cloudron.
Just thought I'd chime in and say I'm very interested in a mail archive solution.
@girish I just restarted my server after some security updates went through and SSHFS stopped working for me as well. I deleted the backup destination and added it again and it started working. I've been on 6.3.5 for a long while (perhaps since it's release) for reference...
@girish Thank you! Sadly, without the ability to pass other content in JSON, I won't be able to use a remote Apprise instance with Uptime Kuma.
Hi all! Really loving Uptime Kuma and wanted to know if anyone has tips on how to setup webhooks in there. I am running a separate Apprise API docker container on another machine (secured via Nginx and ACLs) and am thinking the only way I could pass notifications off is by using the webhook notification option in Uptime Kuma. There isn't much documentation on how to format the webhook and I was curious if anyone can offer some help.
For reference, I'm able to fire off notifications using the curl command like this:
curl -X POST -d '{"urls": "gchat://xxx/yyy/zzz", "body":"test message"}' -H "Content-Type: application/json" https://user:password@domain.tld/notify
OR
curl -X POST -d 'urls=gchat://xxx/yyy/zzz&body=test message' https://user:password@domain.tld/notify
@marcusquinn said in Apprise Notifications:
Hey all! It might be worthwhile circling back on this. Seems like there's a docker image now. I'm not a developer by trade and don't really know if it's any more feasible to integrate into Cloudron, but testing the docker container locally has worked flawlessly!
@girish You are 100% right. I'm new to a lot of this. Thank you again for all of your help!
@timconsidine Thanks for this! I'm not sure how much of my issue had to do with my Mac environment but I was able to get it all setup using Ubuntu using your method and it worked like a charm!
This looks like exactly what I've been looking for for a really long time! Thanks for bringing this over to Cloudron. 
I tried installing it via Cloudron CLI from my Mac and it's throwing an error when I run cloudron build. It's my first time installing a 3rd party app, so maybe I'm doing it totally wrong.
I signed into my Cloudon instance in CLI, cloned the repo onto my computer, went into the directory, and typed cloudron build.
I've made sure my Node instance is up to date (using Homebrew) and I also have Docker installed via Homebrew as well.
Any help would greatly be appreciated!
Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f
invalid argument "git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f" for "-t, --tag" flag: invalid reference format: repository name must be lowercase
See 'docker build --help'.
node:child_process:903
throw err;
^
Error: Command failed: docker build -t git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f -f Dockerfile /Users/michael/Downloads/cloudron-uptime-kuma-app
at checkExecSyncError (node:child_process:826:11)
at execSync (node:child_process:900:15)
at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:187:5)
at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:349:9)
at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31)
at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14)
at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18)
at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12)
at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10)
at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:261:9) {
status: 125,
signal: null,
output: [ null, null, null ],
pid: 9877,
stdout: null,
stderr: null
}