Skip to main content

SFTP Host Key Update

Updated over a month ago

What

Concierge is updating the SFTP Server Host Key. The migration will be finalized on Jan 13, 2026, at 8 am Pacific.

However, the new server is available immediately for early transition.

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

We have introduced a new hostname (filestash.sea1.medallia.com) that is already active. You have two choices:

  1. Switch Now (Recommended): Update your configuration immediately to avoid any disruption on the maintenance date.

  2. Wait until Jan 13: If you continue using the old hostname, your automated connections will fail on Jan 13 until you manually update the keys.

How to Prepare Your Automated Systems

Please choose one of the following options. We strongly recommend Option 1.

Option 1: The Proactive Method (Recommended – Zero Downtime)

You can update your SFTP client or automated script right now to point to our new specific hostname. This allows you to validate the connection immediately and ensures you experience no downtime on Jan 13.

  1. Update your SFTP Hostname: Change your configuration to connect to: filestash.sea1.medallia.com (Note: The username and password/credentials remain the same).

  2. Verify the Connection: Ensure your system can connect and upload files.

  3. Troubleshooting:

    • If the connection to filestash.sea1.medallia.com works, no further action is required. You are ready for the migration.

If you encounter issues, please temporarily revert your configuration to the old host (ftp.zingle.me) and contact Concierge Support immediately. It is critical that we resolve any compatibility issues before the Jan 13 deadline.

Option 2: The Scheduled Maintenance Method (Jan 13 Cut-over)

If you choose to keep using ftp.zingle.me, you do not need to do anything today. However, on Jan 13, 2026, at 8 am Pacific, ftp.zingle.me will be redirected to the new server.

At that exact time, your automated connections will fail because the host keys will change. You will need to perform the following steps immediately after the maintenance is completed:

  1. 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).

  2. Connect once manually: The first connection after removing the old key will prompt your system to accept and save the new key.

    • See below for the new Host Key Fingerprints for verification.

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 (e.g., adding -oStrictHostKeyChecking=no to your command line). We recommend using this only if you are unable to perform the cut-over described in Option 1 or Option 2.

New Host Key Fingerprints (For Verification)

If you are switching to filestash.sea1.medallia.com (Option 1) or waiting for the cutover (Option 2), your system may ask you to verify the fingerprint. Please ensure it matches one of these values:

  • ftp.zingle.me / filestash.sea1.medallia.com (ssh-rsa): AAAAB3NzaC1yc2EAAAADAQABAAACAQCmgsnFGXX9W8Und4YCeYRwQSvZkGDub+KFCCRUAn55f/ARxTjz2z4YFRky7AXdabR625gyPIZ32HI5Cb8IuGmG9sA3+zrGZxEcACz+Os69s5q2yiUMT7aQdNr+NN0oenzKKIZndcZVoL1jbImm6LCTKluC34dzKrX0kIdEvNILcZ7czjSil2F47MfkcsErVTNnGXcXYz/dTuTZR99OYqkOnNb1l6q4h+cu1uDjj8Cz3z+w9r0sQoaBk2aCWBSaygBdDkGyxgaxt9fty8d5MBpBxzjhfFvVVTWaw381V81KGKrBfAoUYSvaCiLKyM9pmkML7eRi5TkgqZXLh0YFgIaREQZl6kYCKc3MZR1aoshWcHiWz2dUbn/huTdxFUs1ZniNRX6B+aHEc+BPmGhzd6smeOAULYJuEqH6Eggo2zTTV791saYt35LEuAcJVjU8ENZrKiEA46KBBgQKqpMldp4xJ0sTCqCzyw9Lo5aliBf9z1czdA9n9sIq+VPMid53Kl8KbiX0k1PGBNq61ub106uJCXWK1oj32dVYDKRf1sFNUbabWtwlfUN02QFIOWActahL5uNvlGHEYpzDrlCYH58QOHKB4F4oA0miJDkYg7tgvFIrE3bnmvCxkuV89UzseYqfyYGgfbwgeMn4YZkcb9zBLR7TDu7m6U/FjSTHiUBaoQ==

  • ftp.zingle.me / filestash.sea1.medallia.com (ecdsa-sha2-nistp521): AAAAE2VjZHNhLXNoYTItbmlzdHA1MjEAAAAIbmlzdHA1MjEAAACFBAAjENWZ4J0sw4D4MmnZ1TgSh7fQI8JiPjHp/6/2eieBBKoA447mt+t56gD0KUIxxRQM8kaJ7/8aCn3EQVMGH0WX7wC3O2N9gKJvnbg/ef3/racmKo+sGmpABdbu8THPxHiyJ8gUzi4TmV/uxA3zUwI/fC7buABk4pV/EUHddWEFMZ06GQ==

  • ftp.zingle.me / filestash.sea1.medallia.com (ssh-ed25519):AAAAC3NzaC1lZDI1NTE5AAAAIHl1M/mRDTgBE+e4GzAj0BN0hKSWNQq5mavT8acWxEl4

Did this answer your question?