Your mistake was to run
init on the second host.
init is for creating a repository. What you have effectively done is created two different master keys in the same repository which, to my knowledge, is unsupported. Because the master keys differ, neither host would be able to decrypt objects added by the other host.
In fact, I didn’t think it was even possible to run
init twice! When I run
restic init against an existing repository, I get:
Fatal: create repository at xxx failed: config file already exists
Assuming that this somehow did happen (what version of restic are you using!?) then a
restic check on either host should complain bitterly.
Your best option here is to figure out which key was created by the second system and delete it. Then, use the password from the first computer on the second, and do not run
init against the repository ever again.
Edit: I would guess that you are using two different versions, based on this difference in output:
created restic repository 193a030f3f at s3:https://s3.us-west-1.wasabisys.com/myrepo
created restic backend c24b8999f0 at s3:https://s3.us-west-1.wasabisys.com/myrepo
Note the different text (repository vs backend). Let us know the version on each system. If possible, make the versions match. Restic tries to be backwards compatible, but the binaries are statically linked and so there is very little reason to be running different versions. I suspect the version running on host 2 is old enough that
init doesn’t check to see if a repository already exists.