Nico

@tvarohohlavy yes you are right that the encrypt would have to be changed as well. I think regarding the UI, always show like currently the hidden thing and allow to...

@tvarohohlavy aah okay I understood. I think this would a bit confusing for the user to type in a particular env name and have the server read a different one....

@tvarohohlavy do you want me to take over from what we have discussed?

Excellent work @tvarohohlavy !! Thank you will integrate asap

@tvarohohlavy I'm ready to merge after you answer my two questions above

Hello, I'm unable to reproduce the error on my side. Are you running the latest version `v0.18.4`? Could you try to update to `v0.18.4` and run doctor on all your...

@mmclain-42 1. Enter in the zerobyte container: `docker exec -it zerobyte /bin/ash` 2. Run this command: `AWS_ACCESS_KEY_ID=your-key AWS_SECRET_ACCESS_KEY=your-key RESTIC_PASSWORD_FILE=/var/lib/zerobyte/data/restic.pass restic check -r s3:/ --read-data` And paste the result here. This...

Interesting, and what if you add the `RESTIC_CACHE_DIR` environment as well? Does it still work? ``` AWS_ACCESS_KEY_ID=your-key AWS_SECRET_ACCESS_KEY=your-key RESTIC_PASSWORD_FILE=/var/lib/zerobyte/data/restic.pass RESTIC_CACHE_DIR=/var/lib/zerobyte/restic/cache restic check -r s3:/ --read-data ```

Thanks for reporting, are you using zerobyte with a custom user inside the container? I have not encountered this issue yet. I think if I simply convert this call to...