hello all,
my first post here. I searched the forum but could not find a match to my situation.
Looking for some help to verify if this is user error or a bug.
workstation_pc : W10 with restic 0.12.1
repo_pc: W10 with fixed ip and rest-server 0.10.0 and restic 0.12.1
I have been successfully using the restic + rest-server combo to backup over VPN. Including data integrity check, restoring snapshots and files.
But since about 1 week i can not do anything anymore. I always get the “negative content length” error when i try anything via the rest: protocol. It does not even ask the password. Example at workstation_pc :
PS C:\Users\MyUserId> C:\LocalData\tools\Restic\restic.exe -r 'rest:http://1.2.3.4:8080/MyUserId' snapshots
Fatal: unable to open config file: negative content length
Is there a repository at the following location?
rest:http://1.2.3.4:8080/MyUserId/
on repo_pc the rest-server does not output anything after giving above command. Normally it would print that it saves blobs and such things.
rest-server is started like this on repo_pc 1.2.3.4:
C:\_RESTIC>c:\LocalData\tools\RestServer\rest-server.exe --no-auth --append-only --listen ":8080" --max-size 300000000000 --path "/_RESTIC/RSR" --debug
When i approach the repository locally at repo_pc i can do anything without problem:
PS C:\_RESTIC\RSR> C:\LocalData\tools\Restic\restic.exe -r 'C:\_RESTIC\RSR\MyUserId' snapshots
enter password for repository:
repository 225889fa opened successfully, password is correct
<SNIP LONG LIST>
PS C:\_RESTIC\RSR>
The config file exists and because i can still perform local actions with restic on repo_pc i believe it should be fine? restic check reveals no issues.
PS C:\_RESTIC\RSR> dir C:\_RESTIC\RSR\MyUserId\config
Directory: C:\_RESTIC\RSR\MyUserId
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 12/21/2021 8:01 PM 155 config
Meanwhile i also upgraded to the freshly released rest-server 0.11.0 but that gives the same result.
Does anybody have an idea how to investigate this matter?
Would love to get restic going again via the rest protocol.