SSH Public Keys
Posted: Mon Oct 23, 2023 9:56 am
We have a setup similar to the diagram below. Two Linux servers with static hostnames, but have DNS A records that alternate between Production and Disaster Recovery every 6 months.
We use Syncovery to send files from a Windows Server to PRD-SVR. I've found that the last time we switched servers, the Syncovery transfers stopped because the SSH public keys it had expected to see had changed. In PuTTY if you do this, you get the below warning.
In PuTTY you can add multiple SSH Public Keys so PuTTY won't show those errors and will autoconnect as normal. Below is an example (The SSH Keys shown are randomly generated from a website - "8gwifi.org - Crypto Playground" so aren't used anywhere on my actual system.)
Is there a way to add public keys to Syncovery so when I tell a profile to connect to a server via a DNS name that will change, it won't pause the job?
We use Syncovery to send files from a Windows Server to PRD-SVR. I've found that the last time we switched servers, the Syncovery transfers stopped because the SSH public keys it had expected to see had changed. In PuTTY if you do this, you get the below warning.
In PuTTY you can add multiple SSH Public Keys so PuTTY won't show those errors and will autoconnect as normal. Below is an example (The SSH Keys shown are randomly generated from a website - "8gwifi.org - Crypto Playground" so aren't used anywhere on my actual system.)
Is there a way to add public keys to Syncovery so when I tell a profile to connect to a server via a DNS name that will change, it won't pause the job?