-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Unauthorized: Unauthorized. #166
Comments
That's because the |
I created the token with sudo atticd-atticadm make-token --sub "main" --validity "99 years" --pull "main" --push "main" --de
lete "main" --create-cache "main" --configure-cache "main" --configure-cache-retention "main" --destr
oy-cache "main" > ~/attic_token.txt now, but I'm still getting the error message on one of my clients after executing:
Different approachSomehow I'm getting a different error message, if I use a file for the token: cd /tmp
sudo atticd-atticadm make-token --sub "main" --validity "99 years" --pull "main" --push "main" --delete "main" --create-cache "main" --configure-cache "main" --configure-cache-retention "main" --destroy-cache "main" > attic_token.txt
# send the token to my pc (client)
rsync ./attic_token.txt pc:/home/tornax then on my pc: attic login --set-default nas http://nas:49400 $(cat attic_token.txt)
attic cache create main
thread 'main' panicked at client/src/api/mod.rs:242:79:
called `Result::unwrap()` on an `Err` value: InvalidHeaderValue
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace |
What does your |
default-server = "nas"
[servers.nas]
endpoint = "http://nas:49400"
token = "<chars>\r" |
That extra The Attic client should just strip out trailing line endings when adding the token. Adding a todo for later. |
Now I'm getting
|
This is my
attic
NixOS config:It also seems to be healthy (output of
sudo systemctl status
atticd.service`):I created then a token with the following command:
afterwards, on a client, I'm executing:
but
attic cache create test
gives me the following error message:does anyone know why this happens?
The text was updated successfully, but these errors were encountered: