-
-
Notifications
You must be signed in to change notification settings - Fork 742
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
borg passphrase is incorrect issue, Linux vs. macOS client #8493
Comments
Do you have any chars outside pure ASCII or accent chars in your pw? While it is not a problem for borg to process them, it might be a problem for you to reproduce the exact same utf-8 byte sequence due to keyboard and normalisation differences. If that is the case, change the pw and just use 0..9 a..z A..Z. |
Thank you Thomas for your quick reply :) Yes, I do have a crazy amount of special chars, maybe a bit excessive :S Now I am getting the same error message when I try to change the passphrase from the Linux client executing: I used borgmatic to setup the borg repository and store the password in
with the same result Is there any other way I could change the passphrase? |
That looks incorrect, guess you meant |
Yes, of course, sorry my mistake, I meant The funny thing though, if I run
|
This is interesting, I installed borgmatic on macOS client, and copied over the .borg-passphrase and borgmatic/config.yaml config files
Now I can can list and mount the repository:
Well, it works now to access the repository from macOS client, but I still don't understand why it does not work with borg alone. |
Shouldn't |
Ehrm, yeah, @jdchristensen is of course correct. Somehow I misread and thought the shell was executing the command, but with simple double-quotes, it doesn't. |
Thank you @jdchristensen, I have tried the following commands on the command line:
All give me the same error when running Also, if I don't export BORG_PASSPHRASE I am being prompted for it, once the connection has been established - not sure if pasting works, because I could never type the passphrase on the keyboard. Is there any way I can increase debug info to understand what am I doing wrong? |
line 1 and line 4 should work, 2 and 3 are incorrect. Please note that the last command in @jdchristensen's post has backticks, not single quotes. |
Also note that |
Related: #8496 |
Thank you all for your help. Unfortunately I continue to be unable to run I am able to access the repro via borgmatic though, where I have the following in the config.yaml: I guess I will try to start from scratch with a simpler passphrase and see if that works. As my current passphrase is not accepted I also can not change it with borg - borgmatic does not have the option It would be good though, to be able to access the repro directly from borg without borgmatic, because also Vorta is throwing the same error. |
Does borgmatic do anything special with the passphrase, @witten? |
borgmatic doesn't do anything special with the passphrase—other than it being interpreted through YAML if it's defined directly in the configuration file. But that shouldn't be the case with the Are you sure your shell isn't interpreting the passphrase though? And you're not using the borgmatic container, are you? There's a known issue with
I assume you mean
It will in the upcoming 1.9.0 release! |
Thank you @witten, indeed I am using Here is the config from the Ubuntu 24.04 client:
The config.yaml on my macOS client looks the same but only includes I installed borg 1.4.0 as a standalone binary:
and borgmatic as described in other ways to install
So, I do have a configuration error in my config.yaml, thank you for pointing that out. I will update the configs and try again. I am grateful for your help and sorry to keep you all occupied without any real contribution... but it remains a mystery why borgmatic works and borg does not. Is there anything I could try to debug this? |
I actually wouldn't expect borgmatic to work with this configuration, so I'm not sure what's going on here! That's because |
I just realized something.. Did you by chance initialize your repo with this configuration? Because if so, then your passphrase may be literally set to the string My recommendation is first verify this theory and, if your passphrase is indeed that string, change it immediately because you've shared it on the internet. 😄 And plus, if you get borgmatic and Borg using the same passphrase, then that would likely solve your issue. |
Haha, yes I did initialize the repro with this configuration! How do I export the string with double quotes as my passphrase though? Like this: |
I would expect single quotes to handle that in most shells: export BORG_PASSPHRASE='export BORG_PASSCOMMAND="cat $HOME/.config/borg/.borg-passphrase"' |
Wonderful, that worked! Thank you so much, it all makes sense now :D |
Passphrase is changed too :) Thank you again for your help! |
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
QUESTION
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
Client: borg 1.4.0
Server: hetzner storage box
Operating system (distribution) and version.
macOS Sonama, homebrew install
Hardware / network configuration, and filesystems used.
How much data is handled by borg?
20GB
Full borg commandline that lead to the problem (leave away excludes and passwords)
borg mount ssh://[email protected]:23/~/repro.borg /local/mnt/dir
Describe the problem you're observing.
I have a client running Ubuntu 24.04, borg 1.4.0 which is backing up daily to a hetzner storage box server. I understand how I can restore data from the repository to the client our mount it by following the commands in the FAQ
I want to mount the repository on my macOS client, but running the same command and specifying the correct borg-passphrase I always get error message:
passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND or via BORG_PASSPHRASE_FD is incorrect.
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
I have read through the docs and FAQs and search the web but I can not find the correct documentation. I am sure this has been done before and I am just missing a simple step :S Please be so kind and point me to the right direction.
I can access the hetzner storage box via SSH using a ssh_key, so it is not a SSH issue. I found similar questions on reddit, do I have to init the repository locally to mount it? I am so confused...
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: