Lachlan, creator of lemmyunchained.net

  • 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle

  • LachlanUnchained@lemmyunchained.nettoSelfhosted@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    10
    ·
    edit-2
    1 year ago

    AI GENERATED:


    The ttionya/vaultwarden-backup tool is intended to work with Docker volumes. However, you are using a bind mount, not a named volume. Bind mounts refer to the use of local folders to store data, as in your case (./vaultwarden:/data/), while volumes create a specific place within Docker’s own filesystem for the data.

    Although this tool is designed for volumes, it might still work with bind mounts if the backup container can access the data directory. You would need to modify the volume line in the Docker Compose file for the backup tool to point to the directory where your bind mount is located, i.e., to point it to your local ./vaultwarden directory.

    So, you might want to adjust your docker-compose.yml file like this:

    services:
      vaultwarden-backup:
        image: ttionya/vaultwarden-backup:latest
        container_name: vaultwarden-backup
        environment:
          - PUID=1000
          - PGID=1000
          - BACKUP_INTERVAL=12h
          - PRUNE_BACKUPS=7D
        volumes:
          - ./vaultwarden:/vaultwarden:ro
          - ./backups:/backups
        restart: unless-stopped
    

    In this configuration, ./vaultwarden:/vaultwarden:ro line is the key. It mounts your local ./vaultwarden directory to /vaultwarden inside the backup container (readonly mode), which should allow the backup tool to access the data.














  • Really strange. What von client are you using on android? Im iOS, so not overly familiar. Probably done all this, but just run through it again make sure you haven’t got a typo somewhere or something.

    1.	Check Connection Settings: Ensure the IP, port, and authentication details are correct in JuiceSSH.
    2.	Firewall Rules: Confirm the SSH port (usually 22) isn’t blocked by any firewalls on your network or server.
    3.	Try another SSH App: To see if it’s a JuiceSSH-specific issue, download another SSH client like Termius and test the connection.
    

    (I’d probably start with 3, might narrow it down to a juice config problem, I’m not very familiar with juice)