I suggest you stick with files default locations if not comfortable with changing it - or set rclone config location env variable - check on rclone website its exact name. It is something like RCLONE_CONFIG_FILE
What I would like to add:
I had a working restic setup on windows with a repository to onedrive over rclone. All necessary files (restic.exe, rclone.exe, password-file, my scripts) are located at c:\tools.
So I placed Restic-Browser.exe also there and created a batch file to start it. At the beginning I could not make it work, Restic-Browser would always complain about something like "c:" does not exist. I got it workind then with slashes instead of backslashes
SET PATH=%PATH%;c:\Tools
Restic-Browser.exe -r "rclone:onedrive:/restic-backup" --password-file "C:/Tools/pwd.txt" --rclone "C:/Tools/rclone.exe"
On Kubuntu 22.04.4 LTS, I played around a little bit with v0.3.0:
$ restic-browser --version
** (restic-browser:132952): WARNING **: 18:04:09.438: webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing.
Restic-Browser v0.3.0:
(As an aside, a timestamp without a date is, eventually, useless.)
I mostly liked what I saw. I Very Much liked the readonly behaviour!
The main thing which bothered me is that I could not find any way to “Close” a REPO within the GUI. I could "Open” a REPO using the GUI, but once Opened, it stayed Open; I was unable to find any way of un-Openning a REPO. Being readonly, this (presumably) would migrate any confusions/mistakes (in the case of multiple opened repos), but it nonetheless made me Very Nervous: I did not feel in full control of what the tool might be doing, now or in some future version.
The weird thing is, I also use restic browser with repos on Hetzner StorageBox over sftp. SSH Auth goes over ssh config and id_xxx private key in the background for both. The weird thing is, the configuration is the same for both, for one it works without problems, for the other one, I get
I double checked the sftp URLS multiple times and also the directory content looks fine in both cases and the top-level content is identical.
Also restic check etc. doesn’t show any issues with the repo. Both repos are v2.
UPDATE: solved it. Was a really stupid error. There was a space at the end of the sftp://… URL maybe the GUI could check that or just trim the URL
So to sum and and to make restic browser work with sftp:// URLs:
in restic browser, omit the leading “sftp:” for the URL. It’s already here when you select type = SFTP
make sure you don’t have leading or trailing spaces in the URL
make sure you can connect without password on the CLI to the repo URL (put the required information, which SSH key to usw etc. in .ssh/config - this works in Linux as well as Windows)