rsync is typically used over ssh. That does not use your new certbot ssl cert; perhaps that’s for some other service.
The first change the client is likely complaining about is the new ssh server key that was generated when you re-installed the OS.
You can verify this by trying to ssh from the client to the server as the user that rsync runs under; does it fail with "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!?"
Ssh stores fingerprints for server keys in ~/.ssh/known_hosts on the client; edit that file and remove the lines pertaining to the server (look for hostname and IP addresses).
Then do a manual ssh and accept the new key.
Secondly, if you had setup passwordless connections such that the server sshd trusted the client key, that configuration may have gotten lost when you re-installed.
You may need to re-run ssh-copy-id to add the client key to the server's ~/.ssh/authorized_keys.
Then test if you can run a manual rsync before trying the Gui.
If you’re not using rsync over ssh, then it depends a bit what you actually are doing. Rsyncd itself does not implement SSL/TLS, and folks use things like stunnel to provide secure connections (see eg
http://www.netbits.us/docs/stunnel_rsync.html) and it would get more complicated.
— Martijn
I'm sure this is trivial but I don't know where to look...
My wife's PC uses Grsync (gui for rsync) to backup to my server. I've recently put a new HDD in the server and re-installed everything, including a new SSL cert via Certbot. Now her Grsync refuses to connect because the certificate has changed. I guess sudo apt purge grsync then re-install it would do it but is there a more elegant method? Some config file I can edit or delete?
--
Phil Thane
www.pthane.co.ukTweet @pthane
01767 449759
07582 750607
_______________________________________________
main@lists.alug.org.uk
http://www.alug.org.uk/
https://lists.alug.org.uk/mailman/listinfo/main
Unsubscribe? See message headers or the web site above!