Rest-server - 404 not found (Docker/FreeBSD)

Getting Help
1

Hi everyone,
I’ve been trying to set up an instance of the rest-server on a FreeBSD NAS and on an OpenSUSE server via Docker.

On both instances, I managed to set the server up (the only modification I did is adding the --no-auth parameter as I am just testing for now), but on both instances I get a 404 error (this is when running restic init):

Fatal: create repository at rest:http://[IP]:[PORT]/[PATH] failed: Fatal: server response unexpected: 404 Not Found (404)

I am seeing this error both when mapping to an empty /data directory, or to a directory with pre-existing files.

I’ve read the docs and have yet to figure out what I am doing wrong - any help would be greatly appreciated.

Thank you!

2

I having a similar issue
Debian + Docker + Rest-server
I get 404 on the Ubuntu server when trying to init repo

Fatal: create repository at rest:***
failed: Fatal: server response unexpected: 404 Not Found (404

3

Please tell us the exact restic and rest-server version you are using. What is the exact command you run (you can obfuscate hostnames and foldernames, but preserve the path structure!)? Is there any log output on the rest-server side?

4 
restic version
restic 0.8.3
compiled with go1.10 on linux/amd64

rest-server - Docker Hub

client -

restic -r rest:https://staging:****@****:8000/staging/staging.server --cacert public_key init
Fatal: create repository at rest:https://staging:****@****::8000/staging/staging.server failed: Fatal: server response unexpected: 404 Not Found (404)

server -

 docker run -p 8000:8000 -v /home/rest-backups:/data --name rs_**** -e OPTIONS='--private-repos --tls --append-only --debug' restic/rest-server
Unable to find image 'restic/rest-server:latest' locally
latest: Pulling from restic/rest-server
59bf1c3509f3: Pull complete
c689396b2983: Pull complete
77d4459aca22: Pull complete
2e1bca4de4d1: Pull complete
73994746a884: Pull complete
bf2d6a3d6556: Pull complete
Digest: sha256:df6a790c630f9c6653756fd37cd75d4666634d57a5de58f953cf3bd020e22c09
Status: Downloaded newer image for restic/rest-server:latest

**WARNING** No user exists, please 'docker exec -it $CONTAINER_ID create_user'

Data directory: /data
Authentication enabled
Private repositories enabled
start server on :8000
TLS enabled, private key /data/private_key, pubkey /data/public_key
HEAD /staging/staging.server/config
Reloaded htpasswd file
checkConfig()
stat /data/staging/staging.server/config: no such file or directory
POST /staging/staging.server?create=true
5

I noticed that I was using an old version of restic
I upgraded it and after that, it works as expected.

1 Like