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.

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

@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

@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

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

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
}

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

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

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

@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

Seems like I'm having the same issue. Is there a workaround for this? Not quite sure how to fix it!

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.

Hi all- I'm a bit new to Cloudron and I've been testing Vaultwarden outside of Cloudron for a while (installed as an add-on through Home Assistant) and I need a little guidance on importing my SQLite database from Vaultwarden on Home Assistant to the MySQL database for Vaultwarden in Cloudron.

I can see the database url in the Vaultwarden Admin section, but I'm not quite sure how to connect to it in terminal.

Any help is greatly appreciated!

Thanks!