SFTP host-key fingerprints
When you connect to your Haptic server via SFTP for the first time, your SSH client will display a host-key fingerprint and ask you to confirm it. Compare what your client shows against the row for your server’s region below — they MUST match exactly. If they don’t, do not accept the key. Email support@haptic.gg and we’ll investigate.
| Region | SFTP hostname | SHA-256 fingerprint | Rotated |
|---|---|---|---|
| na-west | sftp-na-west.haptic.gg | SHA256:QHHuXe0dnm4BrsZLUJnxxK4bec6dLIoHTnlvRdG3DGE | 2026-06-13 |
| na-east | sftp-na-east.haptic.gg | SHA256:ScOB6wqBon1Ti8mpXdMcPT6tb2w9g8+IZusipBZhLyU | 2026-06-13 |
| eu-west | sftp-eu-west.haptic.gg | SHA256:Yzqk2SDlZwC/YUOzrCCsqOZHqzPotocIPhEUUoI2j7k | 2026-06-13 |
How to verify
OpenSSH / sftp / scp: on first connect your client will print a line likeED25519 key fingerprint is SHA256:abc...— compare against the row above and answer yes only if they match.
FileZilla: the “Unknown host key” dialog shows the fingerprint in the same SHA-256 format. Match it before clicking OK.
WinSCP: the “Continue connecting” dialog shows both an MD5 and a SHA-256 fingerprint. Use the SHA-256 row.
When fingerprints rotate
ED25519 host keys do not need routine rotation. We only rotate on suspected compromise (extremely rare) or when provisioning a new region for the first time. Rotation events are announced in the changelog at least 24 hours in advance whenever planned.
After a rotation, your SSH client will show “host key changed” — that’s expected. Verify the new fingerprint against this page before accepting it; remove the old entry from your local ~/.ssh/known_hosts with ssh-keygen -R sftp-<region>.haptic.gg.
