Skip to content
Production Console connected but keyboard input not working — PostgreSQL backup blocked
princehennyson-rgb
OP

a month ago

Issue: Railway browser Console does not accept keyboard input

I am running a production Django financial application with PostgreSQL 18 on Railway.

The browser Console displays "Connected" and shows the root shell prompt, but it does not reliably accept keyboard input.

Environment

  • Railway Free/Trial plan
  • Browser: Microsoft Edge
  • Operating system: Windows 10
  • Database: PostgreSQL 18
  • Previous support reference: browser-console-ignores-keyboard-input-f2ff6f3a

Why this is urgent

I need to create a consistent, read-only PostgreSQL database backup, encrypt it with AES-256-GCM, and upload it to an existing private Cloudflare R2 bucket.

My current plan cannot provision another service, and the existing application container does not have pg_dump or pg_restore available.

Assistance requested

  1. How can I restore keyboard input in the browser Console?
  2. Is there a supported method to run a one-time PostgreSQL 18 dump from the existing environment without using the Railway CLI?
  3. How can the PostgreSQL client utilities be made available without interrupting production?
  4. Can this be achieved within current plan limits without purchasing an upgrade?

Please do not restart or modify the production database or publicly expose its connection.

A screenshot of the connected Console is attached.

I would appreciate guidance from a Railway engineer or someone familiar with Railway's browser Console implementation.

image.png

$10 Bounty

2 Replies

Railway
BOT

a month ago

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

Status changed to Open Railway • about 1 month ago


  1. Try using an incognito browser window.
  2. You can run pg_dump through the Console window and download the dump file from the filebrowser built into the Console window.
  3. Using a database client won’t affect/interrupt the service…? (Can you clarify this question?)
  4. Yes.

mxiand

a month ago

One detail to add to the moderator's answer: the Django container missing pg_dump does not necessarily mean you need another service or an application redeploy. Open Console on the existing PostgreSQL service, rather than on Django, and first check:

command -v pg_dump
pg_dump --version
pg_restore --version
df -h /tmp

Railway's standard PostgreSQL service is based on the official Postgres image. Verify the tools are actually present and are version 18 for your server; I cannot confirm your deployed image from this thread.

If the database Console accepts input, the tools exist, and there is enough temporary disk space, use the service's existing PGHOST, PGPORT, PGUSER, PGDATABASE and authentication configuration. Check the selected database/user privately before exporting. Do not print or paste connection strings, passwords, or dump contents here.

umask 077
backup_dir=$(mktemp -d /tmp/pgbackup.XXXXXX) || exit 1
pg_dump --format=custom --lock-wait-timeout=5000 \
  --file="$backup_dir/database.dump" &&
pg_restore --list "$backup_dir/database.dump" > "$backup_dir/contents.txt"
printf 'Backup directory: %s\n' "$backup_dir"

Only treat the dump as successful if both commands succeed; inspect errors and do not use a partial file. This reads the database without restoring into it. It still consumes CPU/I/O and takes shared table locks, so it is not a guarantee of zero production impact. The timeout limits waiting for the initial locks. This is one database's logical export, not a physical/PITR backup or a complete cluster/role backup.

Download the successful archive through the Console file browser as the moderator suggested. pg_restore --list checks archive readability, not recoverability: perform a test restore into an isolated PostgreSQL 18 instance on your own machine, never into production.

For your encryption requirement, do not use openssl enc -aes-256-gcm: OpenSSL's enc command does not support GCM. Encrypt locally with a maintained tool that explicitly supports authenticated AES-256-GCM, retain its nonce/tag and key securely, verify decryption, and upload only ciphertext to your existing private R2 bucket. Do not install utilities or change the database image/start command just to attempt this export.

If input still fails in a clean browser session on the PostgreSQL service too, this route remains blocked by Console access; I do not have a verified keyboard fix or a plan-limit bypass. Can you confirm whether that Console accepts typing and the two client versions? Please omit secrets.

References: Railway PostgreSQL, PostgreSQL pg_dump, OpenSSL enc limitations.

AI-assisted, reviewed against the linked official documentation. I have not accessed or tested your production environment.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...