Railway SSH registration succeeds but service session closes on Windows and WSL
bondarsvetlana096-cyber
HOBBYOP

17 days ago

Railway Support submission draft

Prepared: 2026-08-04 (Europe/London)

Available official channel

The authenticated Railway account is on the Hobby plan. In Railway Central Station, Technical Help is available. The form displays Ask Railway Privately, but that option is disabled for this account. The available submission path is therefore an official public Technical Help thread using Ask the Community.

Expected response indicator shown by the form: usually within 12 hours. This is an interface estimate, not a guarantee.

Exact navigation path

  1. Open https://railway.com/help.

  2. Railway redirects to https://station.railway.com/.

  3. Select Login with Railway if the Central Station session is not already authenticated.

  4. Select Get Help! — Ask the Railway team or community.

  5. Select Technical Help — Get help with deployments, services, or technical issues.

  6. In Service, select:

    wholesome-miracle / siteformo-ai-platform / production — SUCCESS

  7. Keep the available visibility: Ask the Community.

  8. Enter the title and message below.

  9. Attach only the sanitized file listed below.

  10. Stop before Create Public Thread and obtain owner confirmation.

Subject

Railway SSH registration succeeds but service session closes on Windows and WSL

Message

Railway SSH registration succeeds for an owner-managed ED25519 identity, but the SSH session to our production service closes before the safe `pwd` command returns any output.

Affected service:
- Project: wholesome-miracle
- Environment: production
- Service: siteformo-ai-platform
- Current deployment/service status shown in Railway: SUCCESS

Native Windows reproduction:
- Windows 10 build 10.0.19045.6466
- Railway CLI 5.30.3
- OpenSSH for Windows 9.5p1
- ssh-agent: PASS
- Expected owner key offered: PASS
- Railway SSH key registration: PASS
- Project/environment/service resolution: PASS
- TCP/22, SSH banner, and key exchange: PASS
- Final symptom: "Connection closed by 66.33.22.3 port 22"
- Exit code: 1

Ubuntu WSL comparison:
- Ubuntu 24.04 on WSL 2
- Railway CLI 5.30.4
- Railway authentication: PASS
- Separate WSL ssh-agent and expected identity: PASS
- Railway SSH key registration: PASS
- The same `railway ssh ... pwd` validation failed before returning a working directory

The bounded Railway SSH registration was removed after each failed validation. It is currently absent.

Both native Windows and authenticated Ubuntu WSL paths fail after successful key registration. This makes a client-platform-only issue unlikely. Could Railway please investigate the service-side SSH identity binding and session-establishment path for this service, including whether the active runtime supports Railway SSH correctly?

No production application mutations, deployments, restarts, Railway variable changes, Redis reads/writes/scans, environment dumps, provider requests, or real SMS occurred during these diagnostics.

A sanitized evidence report is attached. It contains no private/public key material, full fingerprint, Railway token/secrets, Twilio credentials, phone numbers, SMS content, Message SID, or Redis/audit data.

Attachment

Attach exactly one file:

C:\SiteFormoLab\.stage-artifacts\railway-ssh-service-side-escalation\RAILWAY_SSH_SERVICE_SIDE_ESCALATION.md

Do not attach:

  • RAILWAY_SSH_SERVICE_CONNECTION_DIAGNOSTIC_V1.md because it contains the full SSH fingerprint and generated service SSH username;
  • RAILWAY_SSH_NATIVE_WSL_COMPARISON_V1.md because it contains the full SSH fingerprint;
  • either SSH key file;
  • runner scripts or terminal transcripts;
  • screenshots containing account details;
  • Railway/Twilio configuration or SMS audit data.

Tracking the response

After owner-authorized submission, monitor Railway Central Station:

  • My Discussions → My Threads for the created thread and replies;
  • My Discussions → Inbox for response notifications.

Do not post follow-up diagnostics or additional files without owner review because the available thread is public.

Stop point

The authorized stop point is immediately before pressing Create Public Thread. No thread has been created and no file or message has been transmitted.

Status: RAILWAY_SUPPORT_PUBLIC_TECHNICAL_HELP_SUBMISSION_READY_OWNER_CONFIRMATION_REQUIRED

$10 Bounty

2 Replies

Railway
BOT

17 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 17 days ago


Your image may not contain a shell. Try adding bash to your image (via a Railpack config file or Dockerfile).


bondarsvetlana096-cyber
HOBBYOP

16 days ago

Thank you for the suggestion.

We verified the exact production runtime image, and the missing-shell hypothesis does not apply here.

The service is built with Railpack using:

  • runtime image: ghcr.io/railwayapp/railpack-runtime:mise-2026.7.15
  • base image: debian:bookworm-slim

Both /bin/bash and /bin/sh exist and are executable in the final runtime layer. Exact validation passed:

  • /bin/bash -lc 'echo RAILWAY_SHELL_READY'
  • /bin/sh -lc 'echo RAILWAY_SH_READY'

The application also starts normally, and production /health returns HTTP 200.

Railway SSH key registration still succeeds, but the SSH session closes immediately before returning a working directory on both native Windows and authenticated Ubuntu WSL.

Could you please advise what Railway SSH expects beyond an available executable shell, or whether this may require service-side inspection of session establishment, user mapping, working-directory resolution, or Railway SSH runtime injection?

No production changes were made during this validation.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...