2 months ago
Hi,
On Pro plan, the built-in Postgres DB interface is permanently stuck on:
"Database Connection — Attempting to connect to the database..."
Status:
- Deployment: Online
- Required Variables: All present
- External connection via n8n: Works perfectly
- Only the built-in Railway DB UI fails
Tried: multiple browsers, incognito, hard refresh. Same result.
Happened after upgrading to Pro. Any fix?
Thanks
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Open Railway • about 2 months ago
2 months ago
The built-in DB browser is a known flaky component — this isn't specific to Pro, but it does get reported more often after account changes (possibly a session/token issue on Railway's side).
A few things to try:
1. Force a fresh session
Log out of Railway completely, clear cookies for railway.app, log back in. The UI sometimes caches stale auth tokens that break the internal connection.
2. Check which URL the UI is using
The DB browser connects via Railway's internal proxy, not the external URL. If your database has a custom DATABASE_URL override pointing to an external host, the UI may be confused. Verify the variable isn't manually set to the public URL.
3. Use the Railway CLI as a workaround
railway connect This opens a direct psql session and bypasses the browser UI entirely.
4. External client with DATABASE_PUBLIC_URL
Since n8n already works, you can use TablePlus, pgAdmin, or DBeaver with the DATABASE_PUBLIC_URL variable — functionally identical to the built-in UI.
If none of those help, open a support ticket via the Railway dashboard. On Pro you get priority support, and this type of issue (dashboard UI broken for a specific account after plan change) usually needs them to inspect the session on their end.