Borg remote backup does not initialize public key, if set up while containers are running

[frederikb96]

First of all, thank you very much for the nice new remote feature. I discovered this bug:

Steps to reproduce

0. Containers are online and running

1. No backup configured yet, I will configure it now
   

2. Insert the url from borgbase and click submit
   

3.No public ssh key is shown:

4. I also checked the log, this is still my log from my previous last run with my local backup, so old log, nothing new here

5. I also checked the volume, and no id_borg there yet

How it worked anyways

I clicked on create backup again, which stops the containers, and then it initializes the repository and I get the pub key. I assume, the problem is that it does not initialize the backup when the containers are running when backup repo is set up :)

[szaimen]

Cc @timdiels

[phillipplum]

Try looking in the backup logs, the first thing it says is: "Your public ssh key for borgbackup is: xxx"

[frederikb96]

Thanks for trying :) But I wrote that I did that and log showed that actually nothing happened, no Borg container started at all, the GUI button click simply didn't trigger correctly if containers are online.

I fixed this easily by just stopping the containers and then registering the backups, so this is not a problem that stops me from using the new feature.

I just opened the issue to help improving edge cases in the future and to make it more usable for others 🙂

[szaimen]

Hey, thanks for this but I think this only happens if you formerly used local backup and change to remote. On a new instance this is not happening in my testing...

[frederikb96]

OK perfect thanks for testing 👍🙂

[szaimen]

A workaround is to remove the borgbackup container and reload the aio interfacd if you run into this state - moving to discussion for now.