Hi!

I'm thinking about using Borg and your container as a solution to backup my unraid-server(!). As much as I understand it, there is always the speaking of a server to backup clients to... This isn't what I would like to do.

I would like to use your container to backup - using borg - to a minio-s3-bucket I created at my 'backup-server'.

If this is of no problem and you do know where to get a howto - I kindly ask for your advice on this topic.

 

Kind regards,

On 1/1/2025 at 4:30 PM, bigggtuna said:

How do I actually make a backup with the default settings? I've followed every issue here and I got to the point where the logs showed the connection from the client was accepted, but the client gives an error that it doesn't have permission to write to '/backup' or '/backup/borg' like kiwijunglist outlines below:

 

I did some digging and found that my authorized_keys file in ~/.ssh/ starts with

restrict,command="cd /backup/id_rsa.pub; borg serve --restrict-to-path /backup/id_rsa.pub "

which seems to limit the clients access (via the -restrict-to-path argument) to only the id_rsa.pub file. I changed the --restrict-to-path argument to allow access to the entire /backup directory and I was finally able to make a backup. The backup finished with warnings that some cert files changed during the process, however, and the authorized_keys file reverts back to the original on an update or container stop/start.

 

Did I set something up wrong to restrict access to the /backup directory? Am I backing up to the wrong target directory?

I had the same problem of not having permission to write to '/backup' - I finally figured out that it was expecting to find a folder within the backup folder with a name matching the key file's name. E.g. for a key named "id_borg.pub", I had to configure the client (in my case, Nextcloud AIO) to backup to the folder '/backup/id_borg.pub". I don't have any experience with other clients, but I hope this helps!

How do i actually talk to the borg Server? (I am using the 1.4 branch instead of latest)

My container starts and creates a folder with the same name as my public key (FedoraWS). That is expected and i take that as a sign i have done the ssh key part correctly. There are no errors in the container log.

It is my understanding that i know need to create a repository from my client machine using borg init.

Before doing that i told borg what keyfile to use by setting the env. variable like this:

export BORG_RSH='ssh -i /PATH/TO/PRIVATEKEY'

My borg init command looks like this:

borg init --encryption=MyPassword ssh://[email protected]:2222/backup/FedoraWS

When i press enter nothing happens. Literally nothing. No Error, no activity nothing.

I am just staring at this in my console (the path in front of it has disappeared):

>

When i look at the server it is doing nothing. No repo being created nothing loged.

Not sure what i am doing wrong given i don't get an error message, or anything at all :)

EDIT:

Turns out i am a bit stupid, instead of giving it my password (which contained special characters it couldn't process...) you literally put the word "repokey" there. It tells it to use a key for encryption, not what key is used. I found this out by using a password without special characters and now i am actually getting an error message!

Remote: [email protected]: Permission denied (publickey).
Connection closed by remote host. Is borg working on the server?

I will investigate further

Edited July 25, 2025Jul 25 by Lukas52
Made some progress

I have fixed my problem.

For reasons i don't understand my BORG_RSH wasn't set the way i told it...

It is working now.

Hi, this post had helped me so much and my borgserver is working fine. But I have this problem:

The publickey is accepted but suddenly the connection is closed. I use ssh to connect my unraid server every day.

My client is Fedora Workstation and I can't find the problem.

What am I doing wrong?

I have solved it. The problem was that I don't read well☹️.

This is the correct config (I forgot the "dot" between the slash).

Edited July 28, 2025Jul 28 by noecu
text lost