12 days ago
We need a read-only PostgreSQL backup and an isolated restore test, without changing production or exposing the database publicly.
Railway CLI 5.71.0 on Windows reaches ssh.railway.com, but first-connection host verification remains unresolved. Your staff replies indicate there is no published authenticated host-key verification channel.
What supported workflow do you recommend for securely exporting a logical backup and testing restoration? Please explain any associated costs. We are requesting guidance only, not infrastructure changes.
1 Reply
12 days ago
The ssh.railway.com endpoint runs on multiple hosts, each with its own key, and those hosts change without notice. We don't publish a fingerprint list, known_hosts entry, SSHFP record, or host CA, and we can't confirm any fingerprint you see. How you handle host key trust for a railway ssh session where you run pg_dump is your decision, and we don't have a recommended procedure for it.
For an isolated restore test, the supported path that leaves the source database untouched is a point-in-time recovery restore, which creates a new sibling PostgreSQL service and never modifies the original. PITR has to be enabled on the database first, though. Enabling it is a configuration change that deploys the service by default, and it only covers history from the point it's turned on.
A normal volume backup restore is not an isolated test. In the dashboard it stages a volume swap that redeploys the original service, and the CLI's backup restore overwrites the database in place.
On costs: a restored sibling service and its volume are billed as ordinary usage while they exist, and PITR archives are stored in a storage bucket that is also billed as usage. You can delete the test service once you've checked the restore.
Status changed to Awaiting User Response Railway • 12 days ago
5 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 5 days ago