atuin: Unable to sync on new devices
I have the same problem as Issue #362.
That is, I am unable to sync atuin on a new device. I have the error message
thread 'main' panicked at 'failed to decrypt history! check your key: failed to open secretbox - invalid key?
Location:
atuin-client/src/encryption.rs:97:22', /build/source/atuin-client/src/api_client.rs:143:45
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
I tried to run the same atuin logout; atuin login -u usernamehere -p passwordhere -k keyhere; atuin sync. The machine which sync worked always successfully ran the commands, while the machine failed to sync always failed with the above message.
I tried to remove everything under ~/.local/share/atuin/ and ran the command again, it also didn’t work.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 22 (8 by maintainers)
@Anagastes I’m really sorry but at no point have I ever said that “self hosted sucks and can’t be debugged…”.
I’ve said I’d rather that people open their own issue if they’re self hosting, and provide all the details about their own specific setup. I find large issues involving a whole bunch of people like this VERY difficult to follow. I’d need debugging cycles with each of the 11 people in this issue, all in one place, when github issues do not support threading.
I’ve said that self hosted setups differ tremendously from user to user - some run the binary, some use docker, some use kubernetes, I know some people using Nomad. Some host on Linux, some host on mac, some use postgres, some use sqlite, etc etc etc. Without all of that information from each person with a problem, it’s really hard for me to do anything at all.
GitHub does not allow me to specify that I am closing this issue in preference of another, which I linked above - #1199. In 1199, people debugged the same problem and got further than this issue here. Which is why I have closed this one, in preference of that.
See where “not planned” can also mean “dupe”.
I’ve countless hours reworking sync to be way more flexible, and totally eliminate this problem for everyone.
So to be honest, it really sucks to be called arrogant. I’m sorry you feel that way about me. I’ve done nothing but try and help. In your own words, I don’t like to be treated like this when I only wanted the best.
Can your clarify what is “not planned” here? For my part I on your hosted version and several other users have confirmed that hooking up more than 2 machines is a problem.
I have a modified version of this story.
I initally set up my
autininstall on one Arch Linux machine using the auto setup script. I created my account there on the public server, and did my initial import and sync.I then set up
autinon a second Arch Linux machine using a similar system setup as the first. The import and sync there worked as well.Now, I’m only able to sync on the second machine, and all other machines, both the first, and any additional I configure thereafter, all give the same error about the key. I did a comparison of the keys on the first two machines using
sha256sumandmd5sumand both files have identical hashsums. I usezshon all machines.I have the same error.
I have atuin running as my own server. The login and sync from the main account (with which the user was also created) works.
On the new PC, the login works, but the sync with the key does not. Here the debug output.
Oh and i’m running manjaro stable with zsh and with atuin 11
The server runs under debian with last atuin release from git