I can run /bin/restic_backup.sh without issue, but the restic-backup service fails to connect to the b2 container

[cpeterp]

Running this on Debian 11 server after installing the systemd version via the makefile.

I was able to run the /bin/restic_backup.sh script with no issues on the initial backup. However, when the timer triggers and the service runs, it fails. I see the following messages after running $ journalctl -u [email protected]

Jan 08 00:00:17 fileserver systemd[1]: Started Backup with restic to Backblaze B2.
Jan 08 00:02:53 fileserver cat[1110507]: Fatal: unable to open config file: Stat: 401
Jan 08 00:02:53 fileserver cat[1110507]: Is there a repository at the following location?
Jan 08 00:02:53 fileserver cat[1110507]: <MY-S3-BUCKET>
Jan 08 00:02:53 fileserver systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Jan 08 00:02:53 fileserver systemd[1]: [email protected]: Failed with result 'exit-code'.

I can only guess that the service fails to properly set up the environment files, so restic isn't able to connect to my backblaze buck, but I'm not sure.

Again, manually running restic_backup.sh works without issue.

[cpeterp]

I discovered the issue was with restic (as well as my own oversight). It looks like restic no longer reccomends using the b2 interface and instead recommends using the s3 protocol. While I had set my RESTIC_REPOSITORY variable to the s3 endpoint of the bucket, restic saw the B2_ACCOUNT_ID and B2_ACCOUNT_KEY, which I guess confused it.

I replaced the B2_ACCOUNT_ID and B2_ACCOUNT_KEY variables with AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY respectively and its working as expected now. Originally, it had worked because I had these variables set in my bash, so my first backup worked.