On the new Railway mobile app, I'm unable to see all the organizations I'm part of.

Description: WoW-style micro-MMO with browser client and persistent multiplayer Category: Other URL: https://railway.com/deploy/world-of-claudecraft

Currently, when attaching a custom domain to a Railway service, the original Railway URL (e.g., myapp.up.railway.app) remains publicly accessible. This creates a duplicate content issue for SEO — search engines may flag the same content served on two different URLs as duplicate, potentially harming search rankings. Current behavior: Railway URL stays active alongside custom domain Only option is to delete the URL entirely (irreversible) No way to temporarily disable without losing the URL Requested behavior: Add a "disable" toggle separate from the delete button Disabled URLs return 404 or redirect to the custom domain Can be re-enabled later if needed Preserves the URL without it being publicly accessible Use case: Users with custom domains need a way to prevent duplicate content indexing while keeping the option to re-enable the Railway URL for testing/debugging without recreating it. is this actually possible on Railway's infrastructure - I want to temporarily disable the staging URLs once my custom domain is attached - without deleting it?

Description: AI agent memory API with FastAPI and Moorcheh retrieval Category: Other URL: https://railway.com/deploy/memanto

Railway doesn't have native connection pooling for Postgres today. Without it, your database can quickly run out of connections as your app scales — and the workarounds are too manual. We're adding one-click PgBouncer connection pooling that works on any Postgres setup, including high-availability clusters. Enabling or disabling pooling won't restart your database. You'll get a pooled DATABASEURL by default (transaction mode) plus an unpooled DATABASEUNPOOLEDURL for operations that need a direct connection like migrations, LISTEN/NOTIFY, and CREATE INDEX CONCURRENTLY. Pool mode is selectable (transaction, session, or statement) and changeable anytime without touching your database. What connection pooling features matter most to you? Drop a comment!

Service: Node.js Express + Apollo GraphQL Issue: Outbound HTTPS streams to AWS S3 stall mid-transfer approximately 1/300 requests What happens: 1. GetObjectCommand is sent to S3 — succeeds, headers received with HTTP 200 2. Stream body begins transferring (100kb file) 3. Stream silently stalls mid-drain — no error, no RST, no FIN, just stops delivering data 4. Hangs indefinitely until something kills the connection (4 minutes) What we've ruled out: - Not an S3 issue — never happens when the same code runs locally - Not a code issue — headers arrive fine, only the body stalls - Not a retry issue — the AWS SDK sees a 200 and considers the request successful, so it never retries - Only affects S3 (outbound HTTPS streaming) — Postgres and Redis connections on the same service are stable Key detail: The failure is completely silent — no error event is raised on the stream, no exception is thrown. The stream just stops emitting data events mid-transfer and never emits end. This suggests something in Railway's network layer is dropping packets mid-stream without closing the connection, rather than actively terminating it. Suspected cause: Railway's egress network (NAT gateway or outbound proxy) is silently dropping packets mid-stream on outbound HTTPS connections approximately 1/300 times. Because no RST or FIN is sent, the TCP connection appears open but data stops flowing. Questions: 1. Is there a known idle or mid-stream timeout on outbound connections from Railway containers? 2. Is outbound traffic routed through a proxy or NAT gateway that could be dropping packets? 3. Are there any known issues with outbound HTTPS streaming to AWS S3 specifically?

I had a build failed for a service and later redeployed successfully with another updated code, but the notification stays, is there a way to dismiss the notification? 19AA013C-6323-446E-9EA7-2595ACBA6978.jpg

Description: Cassandra-compatible ScyllaDB for Railway with volume and private CQL. Category: Other URL: https://railway.com/deploy/scylla-db

Im trying to create new Postgres instance but its stuck in Attempting to connect to database stage. Tried restarting it couple of time and also deleted and created again, but still same issue Screenshot 2026-06-20 at 1.09.50 PM.png

Hi, I'm having an issue with my Postgres service that I haven't been able to resolve after multiple attempts. Root cause (identified): During a session where I was integrating OneSignal, a railway up command was accidentally sent to the Postgres service while the CLI was linked to it instead of my backend service. This deployed my React frontend code into the Postgres container instead of the PostgreSQL image. Current state: - Source Image in Settings: correctly shows ghcr.io/railwayapp-templates/postgres-ssl:18 - I've done a full Redeploy (not just Restart) from the Railway dashboard — it reported success, but Postgres still doesn't respond - TCP connections are accepted on port 5432, but the PostgreSQL handshake never completes (timeout, not connection refused) - CPU: 0%, Memory: 0B in metrics - Volume: 65MB used / 434MB total, PGVERSION=18, all pgdata files present — data appears fully intact - Both private network connections (from my backend via postgres.railway.internal) and external connections (via acela.proxy.rlwy.net:32995) time out What I need: Even though Settings shows the correct image, I believe the running container still has the wrong code (React frontend). The Redeploy didn't seem to replace it. Can you force a clean container provision from the configured image (postgres-ssl:18) on your side, or confirm what is actually running in the container right now? Project details: - Project: ticket agent - Project ID: fabb2fd6-278a-4750-bf84-984b55ed8a51 - Service: Postgres - Service ID: 3dc61420-a50d-4974-a3a4-44cda04b422a - Environment: production Data integrity is critical — I have users depending on this and my last backup is from June 12. Thank you.