I exported a configuration then imported it to set up a duplicate backup to a different machine. The config included a url to the sever with the server fingerprint in it. I changed the server after import in the configuration menus via the GUI and tested the connection (no error reported); the ssh connection worked fine from the console. Yet the backup up failed because of the server fingerprint. The user interface doesn’t seem to give any access to the server fingerprint. It was necessary to edit it out manually in the config file before (re)importing it.
This could be improved in one several ways:
- remove the fingerprint if the server is changed
- make sure the test connection also checks the fingerprint
- expose the fingerprint and allow its deletion