Skip to content
SSH key registration fails with “Problem processing request”
Anonymous
OP

4 hours ago

In Account Settings → SSH → Add New Key, Railway repeatedly returns “Problem processing request” after I submit a public Ed25519 key. I retried with a simple name and the public key on one line without its trailing comment. The key still does not appear under Your SSH Keys. What can I check to resolve this? Is there a supported way to retrieve the source files from an active deployment without restarting or redeploying it if SSH registration remains unavailable?

Awaiting User Response

1 Reply

Railway
BOT

4 hours ago

Two other supported ways to register a key are the CLI commands railway ssh keys add --key ~/.ssh/id_ed25519.pub --name "laptop" and railway ssh keys github. The second one imports the keys from your linked GitHub account. Run railway login first, because key management doesn't work with a project token. Once the key is registered, railway ssh keys should list it. The SSH docs cover both commands.

All of the file access options rely on an SSH connection, so none of them gives you a way around key registration. That includes scp and sftp, the dashboard Console and Files views, and the railway volume file commands.


Status changed to Awaiting User Response Railway • about 4 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...