Restic -r rest:http://host:8000/ command not found


I feel stupid, but I’m missing something here.

restic -r rest:http://host:8000/

Reports list of options as it were an unknown syntax, while I’m using restic without issues diary.

Any hint?


You are missing an actual restic command. Append one of the commands you want restic to perform, see restic help or restic help <command> for more info.

1 Like

ah… ok… so init I.E for starting backup… etc…


(So stupid… sorry).

BTW… I’m trying to make it work with Rclone…

I followed this restic · Using rclone as a restic Backend

But I’m not sure if I understood the example. Where on the process can I put the real restic-server Server?..

rclone serve restic --addr localhost:8889 --user foo --pass s3kr1t remote:bucket/path >> it says to Rclone that there is a restic server on localhost:8889?

restic --repository rest:http://foo:s3kr1t@localhost:8889 init

Where can I put my real restic-server IP?


The usual way to use rclone is to let restic start it:

restic --repo rclone:b2prod:yggdrasil/prod-serverA init

For this to work you have to configure a rclone backend called “b2prod”. That would be the place to put the server address.

I’m confused now. If you have a rest-server running somewhere, then there’s no need to use rclone. Just use a repo url as in the original post.

ok… so restic --repository rest:http://foo:s3kr1t@ init (I.e… for IP Thanks

Almost. It’s --repo (or -r), but the rest is right (assuming you have a rest-server running on that IP and port of course). When you’re done initing your new repository, you can use the backup command instead of init to start backing up your files.

Please take a moment to familiarize yourself with the restic CLI by running rustic help and restic help <command>, e.g. restic help backup :slight_smile: There’s also the documentation at .

1 Like

Thanks a lot. Believe me, I read it. I was not sure the way restic works with its rest server. Now it’s clear.

Additionally, I’m looking for add rclone on this since it provides me an easy setup for the backend configuration, and a transparent encryption overlay that doesn’t depends on the first layer (restic). Supposing that restic has (surely not) any kind of error on the implementation, this second layer makes quite difficult (but not impossible of course) what is on the second layer (restic or other). On top, brute force attacks in case they where able to work, are on this approach, even harder.

That’s the reason why I’m trying to use restic server as another backend (I suppose it was implemented in this way) as SFTP, Google Drive or other on rclone.


1 Like