Output of rest-server --version

f41f6db080c5

How did you run rest-server exactly?

Using docker-compose with the following compose file:

version: '2'

services:
  restserver:
    volumes:
       - fs-restic:/data
    image: restic/rest-server:latest
    environment:
      - VIRTUAL_HOST=$DOMAIN
      - VIRTUAL_PORT=8000
      - LETSENCRYPT_HOST=$DOMAIN
      - OPTIONS=--private-repos --debug
    networks:
      - web

networks:
  web:
    external:
      name: webshare

volumes:
  fs-restic:
    driver_opts:
      type: "nfs"
      o: "addr=10.0.0.3,nolock,soft,rw,intr,rsize=8192,wsize=8192,timeo=20,retrans=3,proto=tcp"
      device: ":/mnt/storage/dockerhost/rest-server"

Using nginx-proxy, the rest-server is available on https://$DOMAIN with a valid Lets Encrypt certificate.

What backend/server/service did you use to store the repository?

Docker volume that is mounted via NFS from another VM (as it can be seen in the docker-compose.yml above).

Expected behavior

I used Minio S3 to serve the restic repository for one of my backed up systems before.
I expected to be able to migrate the folder containing the restic repository to the NFS volume and switch my backup script to use rest:https://... to continue using the already existing repository.

Actual behavior

However, if I do so and run restic cat config afterwards, the output is something like this:

repository 426ac560 opened (version 2, compression level auto)
List(lock) returned error, retrying after 552.330144ms: List failed, server response: 404 Not Found (404)
List(lock) returned error, retrying after 1.080381816s: List failed, server response: 404 Not Found (404)
List(lock) returned error, retrying after 1.31013006s: List failed, server response: 404 Not Found (404)
List(lock) returned error, retrying after 1.582392691s: List failed, server response: 404 Not Found (404)
List(lock) returned error, retrying after 2.340488664s: List failed, server response: 404 Not Found (404)
List(lock) returned error, retrying after 4.506218855s: List failed, server response: 404 Not Found (404)
List(lock) returned error, retrying after 3.221479586s: List failed, server response: 404 Not Found (404)
List(lock) returned error, retrying after 5.608623477s: List failed, server response: 404 Not Found (404)

Steps to reproduce the behavior

• Create a restic repository and backup something to it (locally).
• Set up rest-server with the docker-compose.yml above.
• Create a set of credentials and input them to the htpasswd file.
• Create the corresponding folder structure and migrate the already existing restic repo to the NFS volume of the rest-server instance.
• Switch the backup script to use the new repository location.
• Run restic cat output.

For reference, here is the snippet of my backup script:

#!/bin/bash

set -e

# Set crypto passphrase for encryption
export AWS_ACCESS_KEY_ID=forgejo-dev
export AWS_SECRET_ACCESS_KEY=123secret
export RESTIC_PASSWORD=456secret
export RESTIC_REPOSITORY=rest:https://$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY@$DOMAIN/forgejo-dev/forgejo-dev-backup
restic="/opt/restic/restic"

$restic cat config
exit 0

Interestingly, if I create a new repository with a different name using the backup script (on the rest-server location), everything works correctly and the files can be backed up. I conclude that my credentials and repo config within the script and the htpasswd file should be correct.

Do you have any idea what may have caused this?

• Maybe I missed something.
• Maybe file permissions? (Though, I checked these.)

Do you have an idea how to solve the issue?

• No :(

Did rest-server help you today? Did it make you happy in any way?

rest-server is amazingly fast, especially in comparison with the Minio S3 backend :-).
Thank you for your help!