Cloudron Forum

Just thought I'd chime in and say I'm very interested in a mail archive solution.

Of course, you always figure things out after posting, so I thought I'd do a mini-writeup on exporting your Vaultwarden database from the Home Assistant installation and bringing it into Cloudron's instance. Doing so brought over all of the users and organizations that were created before.

1. I followed this guide to take a SQLite dump of my Home Assistant Vaultwarden database.

2. Once I had the dump, I opened the web terminal for Vaultwarden in Cloudron and uploaded the dump to /tmp

3. Once the database was finished being uploaded, I put Vaultwarden in recovery mode (found under the repair section)

4. After, I clicked on the "MySQL" button, which pasts in the command to connect to the Vaultwarden database in Cloudron. Don't press enter - simply add the following after the connection string: < mysqldump.sql
   The string should look something like this:

mysql --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE} < /tmp/mysqldump.sql

After completing these steps, I took Vaultwarden out of recovery mode, went to the admin page, and confirmed all users exported successfully.

@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.

@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!

@marcusquinn said in Apprise Notifications:

https://github.com/caronc/apprise

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!

https://github.com/caronc/apprise-api

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.

@girish Thank you! I was already on 6.3.5 and was experiencing that issue. I decided to delete the /mnt/cloudronbackup directory and set the SSHFS settings again (I had already reset the SSHFS settings with no success) and it works now. The permissions of the new cloudronbackup directory are totally different.

Initially, the cloudronbackup directory was root:root. Then I got a warning saying it should be yellowtent:yellowtent- it still didn't work after making that change.

Not Working:
drwxr-xr-x 3 yellowtent yellowtent 4.0K Jul 11 21:33 cloudronbackup

Working:
drwxrwxrwx 1 1032 users 100 Jul 12 14:09 cloudronbackup

@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!

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

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.

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.

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?

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!