Nold360 / docker-borgserver

Dockerimage that runs a Borg backup server, accessible by ssh using publickey authentication
40 stars 24 forks source link

question: ssh connection error. #4

Open budda85 opened 5 years ago

budda85 commented 5 years ago

Hey, I'm running your borg-server on my Synology NAS. I've added my pub Key in the /sshkeys/client Folder and start the Container. The container found the Key and import it. But when i try to init my repo there is a permission denied error. The Container see my connection, but is it normal that the port ist increase with every try? Did you have an idea?

Here the log from the Docker:

date stream content
2019-10-10 07:56:10 stdout Connection closed by authenticating user borg 172.17.0.1 port 36208 [preauth]
2019-10-10 07:55:54 stdout Connection closed by authenticating user borg 172.17.0.1 port 36207 [preauth]
2019-10-10 07:55:31 stdout Server listening on 0.0.0.0 port 22.
2019-10-10 07:55:31 stdout Server listening on :: port 22.
2019-10-10 07:55:31 stdout * Init done! Starting SSH-Daemon...
2019-10-10 07:55:31 stdout ########################################################
2019-10-10 07:55:31 stdout ** Adding client xyz.pub with repo path /backup/xyz.pub
2019-10-10 07:55:31 stdout * Starting SSH-Key import...
2019-10-10 07:55:31 stdout ########################################################
2019-10-10 07:55:31 stdout * Checking / Preparing SSH Host-Keys...
2019-10-10 07:55:31 stdout * Testing Volume SSH_KEY_DIR: /sshkeys
2019-10-10 07:55:31 stdout * Testing Volume BORG_DATA_DIR: /backup
2019-10-10 07:55:31 stdout ########################################################
2019-10-10 07:55:31 stdout * Docker BorgServer powered by borg 1.1.9
2019-10-10 07:55:31 stdout ########################################################

Here is my terminal:

root@xyz:~# borg init ssh://borg@DOMAIN.tld:port/backup/xyz.pub/repo Remote: Permission denied (publickey). Connection closed by remote host. Is borg working on the server?

Thx Jan

Nold360 commented 4 years ago

Hi,

sorry, i really don't know. Did you figure it out yet? I guess it might be something with the owner/rights of the volumes. Or bad ssh-key format.