Domain change

[lshantz]

I don't think it is a bug, but I found something that really causes grief. I set this up a couple months ago and it has worked fantastic! However, I lost my domain name. Long story. So now I have a new domain and I can not modify the repository information. It will not let me edit it. I even tried to find replace the domain in the config file, but that borked it. I have tried adding a new repository and it does not work. I've tried everything. I even un-installed it and re-installed it. I'm kind of at a loss.

I'm getting different error messages depending on what I try.
[Default] ERROR: Connection closed by the remote host. Is Borg working on the server? (It is)
Another time WARNING: Remote: ssh_askpass: exec(/usr/lib/ssh/ssh-askpass): No such file or directory
I found the authkey for the user I'm loggging in with and deleted the ssh key, but clearly something has changed. Do I need to delete the Borg app on the server and re-install?

Another thing I have found is apparently a cron job is added, so uninstalling the program leaves lots of stuff behind. It still keeps giving me errors as it tries to back things up, even though via Cachyos program removal tool, it is still haunting me. I had hoped be starting over from scratch I could get it working again.

[goebbe]

@lshantz There could be several issues.

First, start with your server setup and make sure that you can access your server via borg.
Check, in the following order:

1. Can you do an ssh login to the new server
2. Once you are logged in to the server, can you run borg --version on the server?
3. Can you do an ssh login without a password (using ssh keys)? If not you have to set this up.
4. From your local machine, can you run a simple borg command that fetches information from the borg server

On the Vorta-side you have to adapt the server setting in your (existing) profiles:

1. First select the profiles and "export profiles". This will give you a .json file in your home directory, for each profile.
2. Edit the server information in the .json file, using the text editor of your choice.
3. Re-import the edited profiles - see in the documentation on how-to achieve this.

Hope this helps.

[lshantz]

Thank you for taking the time to reply. It turns out that information was cached and a reboot stopped the constant failure notices. My son discovered that you need a argument in the advanced section to allow it to talk to the Synology server. I sure didn't recall that. I don't recall ever seeing that in the instructions. Kudos to my son. It would be nice if in an existing setup, if it allowed you to see those extra arguments and the ability to make changes, like domain name etc. Overall, an AWESOME backup solution though. That export idea, might do what needed doing, but we are back in business now. Hopefully your thoughtful replay can help others down the road.

[goebbe]

Great, that you were able to resolve the issue!
There are already open feature requests for the ability to view/ change repository settings. All it takes is a developer with some time to spare... 🥲

Currently, there are two workarounds:

1. create a new repository with the correct settings
   or
2. export profiles/ edit the profile.json file / reimport profiles.

[lshantz]

Key word: correct settings! LOL.. I didn't realize extra arguments were needed in the advanced section. I didn't know about export/import. Will try to remember that if I ever need it. Thanks again.