What
Concierge is updating the SFTP Server Host Key on Dec 3, 2025.
Why
The migration and host key update is essential for improving performance and security. As part of this process, the server's security fingerprint (SSH host key) will change.
What This Means for You
After the migration, your SFTP client or automated script will see a new host key. Because this new key will not match the one your system has saved from previous connections, your client will likely treat this as a security warning.
As a result, your automated connections and scripts may fail until you approve the new host key.
How to Prepare Your Automated Systems
Because your file uploads are automated, you will need to choose one of the following two options to ensure your service is not interrupted.
Option 1: The Recommended Method (Secure Cut-over)
This is the most secure method. On the day of the migration (Dec 3, 2025), after we announce its completion, your script's environment will need to accept the new host key. This usually involves removing the old key so the new one can be saved.
Remove the old host key. For many command-line clients on Linux, this involves editing the ~/.ssh/known_hosts file and deleting the line containing our hostname (ftp.zingle.me).
Connect once manually. The first connection after removing the old key will prompt your system to accept and save the new key. Subsequent automated connections should then work correctly.
To help you verify the new key, here are its fingerprints. When prompted, please ensure the fingerprint matches one of these values::
ftp.zingle.me ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCmgsnFGXX9W8Und4YCeYRwQSvZkGDub+KFCCRUAn55f/ARxTjz2z4YFRky7AXdabR625gyPIZ32HI5Cb8IuGmG9sA3+zrGZxEcACz+Os69s5q2yiUMT7aQdNr+NN0oenzKKIZndcZVoL1jbImm6LCTKluC34dzKrX0kIdEvNILcZ7czjSil2F47MfkcsErVTNnGXcXYz/dTuTZR99OYqkOnNb1l6q4h+cu1uDjj8Cz3z+w9r0sQoaBk2aCWBSaygBdDkGyxgaxt9fty8d5MBpBxzjhfFvVVTWaw381V81KGKrBfAoUYSvaCiLKyM9pmkML7eRi5TkgqZXLh0YFgIaREQZl6kYCKc3MZR1aoshWcHiWz2dUbn/huTdxFUs1ZniNRX6B+aHEc+BPmGhzd6smeOAULYJuEqH6Eggo2zTTV791saYt35LEuAcJVjU8ENZrKiEA46KBBgQKqpMldp4xJ0sTCqCzyw9Lo5aliBf9z1czdA9n9sIq+VPMid53Kl8KbiX0k1PGBNq61ub106uJCXWK1oj32dVYDKRf1sFNUbabWtwlfUN02QFIOWActahL5uNvlGHEYpzDrlCYH58QOHKB4F4oA0miJDkYg7tgvFIrE3bnmvCxkuV89UzseYqfyYGgfbwgeMn4YZkcb9zBLR7TDu7m6U/FjSTHiUBaoQ==
ftp.zingle.me ecdsa-sha2-nistp521 AAAAE2VjZHNhLXNoYTItbmlzdHA1MjEAAAAIbmlzdHA1MjEAAACFBAAjENWZ4J0sw4D4MmnZ1TgSh7fQI8JiPjHp/6/2eieBBKoA447mt+t56gD0KUIxxRQM8kaJ7/8aCn3EQVMGH0WX7wC3O2N9gKJvnbg/ef3/racmKo+sGmpABdbu8THPxHiyJ8gUzi4TmV/uxA3zUwI/fC7buABk4pV/EUHddWEFMZ06GQ==
ftp.zingle.me ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHl1M/mRDTgBE+e4GzAj0BN0hKSWNQq5mavT8acWxEl4
Option 2: The Alternative Method (Bypass Host Key Check)
⚠️ Note: This method is less secure as it bypasses an important security check that protects against man-in-the-middle attacks. We recommend using it only if you are unable to perform the manual cut-over described above.
You can modify your script to temporarily or permanently ignore the host key check. The command or setting depends on the software you use.
For scripts using the standard sftp or ssh command-line tools, you can add the following option to your command:
Bash
-oStrictHostKeyChecking=no
For other clients or programming libraries (like Python's Paramiko, JSch in Java, etc.), there will be a similar option in the connection settings, often called setMissingHostKeyPolicy or similar, which you would need to adjust.