a month ago
2026-05-21 00:16:53.112 UTC [14] LOG: starting PostgreSQL 18.4 (Debian 18.4-1.pgdg13+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
2026-05-21 00:16:53.112 UTC [14] LOG: listening on IPv4 address "0.0.0.0", port 5432
2026-05-21 00:16:53.112 UTC [14] LOG: listening on IPv6 address "::", port 5432
2026-05-21 00:16:53.116 UTC [14] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2026-05-21 00:16:53.126 UTC [40] LOG: database system was interrupted; last known up at 2026-05-21 00:16:21 UTC
2026-05-21 00:16:53.493 UTC [40] LOG: database system was not properly shut down; automatic recovery in progress
2026-05-21 00:16:53.498 UTC [40] LOG: redo starts at 0/1D9F468
2026-05-21 00:16:53.521 UTC [38] LOG: checkpoint complete: wrote 0 buffers (0.0%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.005 s, sync=0.004 s, total=0.022 s; sync files=2, longest=0.003 s, average=0.002 s; distance=0 kB, estimate=0 kB; lsn=0/1D9F4A0, redo lsn=0/1D9F4A0
2026-05-21 00:16:53.526 UTC [14] LOG: database system is ready to accept connections
22 Replies
a month ago
Please provide more information
Like what kind of site? Is it yours? An open source one? What errors are you seeing/in the deploy logs?
This is the error I get..
The site is mine... @astrid!!!
Attachments
a month ago
What errors are you seeing/in the deploy logs?
(of your site, not the db)
Attachments
a month ago
That's your postgres service's logs
a month ago
Application failed to respond error is mostly caused by mapping your url to a port your app isn't listening on
a month ago
Deploy logs, not Railway's fallback please!
a month ago
but also what darseen said
This is the deploy logs.
Attachments
a month ago
Deploy logs of the site, not the database please
Attachments
a month ago
Could you show the config in the site service's domains section?
a month ago
Your app is listening on port 8080. Just go to the networking section in your service settings and make sure the public URL is mapped to 8080.
You mean here? That's how I met it.
Attachments
Got it fixed myself with the help of Claude... It's now working...
Had to redeploy the service again... thanks
@astrid!!!
Attachments
4 days ago
Circling back, sorry for the delay. Postgres healthy after a redeploy but the site still down usually means the app service is holding dead connections; redeploy or restart the app and it reconnects. Still seeing it? Tell me the service. Otherwise HA keeps a host failure from cascading. — Angelo