9 months ago
Hey!
I can't access to my tables. Quite strange and unexpected behavior:
DEPLOY LOGS:
Starting Container
Certificate will not expire
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-05-19 23:39:30.770 UTC [5] LOG: starting PostgreSQL 16.8 (Debian 16.8-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-05-19 23:39:30.771 UTC [5] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-05-19 23:39:30.771 UTC [5] LOG: listening on IPv6 address "::", port 5432
2025-05-19 23:39:30.776 UTC [5] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-05-19 23:39:30.789 UTC [28] LOG: database system was interrupted; last known up at 2025-05-19 23:21:33 UTC
2025-05-19 23:39:30.834 UTC [28] LOG: database system was not properly shut down; automatic recovery in progress
2025-05-19 23:39:30.841 UTC [28] LOG: redo starts at 0/1E28480
2025-05-19 23:39:30.841 UTC [28] LOG: invalid record length at 0/1E284B8: expected at least 24, got 0
2025-05-19 23:39:30.841 UTC [28] LOG: redo done at 0/1E28480 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-05-19 23:39:30.865 UTC [26] LOG: checkpoint starting: end-of-recovery immediate wait
2025-05-19 23:39:30.902 UTC [26] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.019 s, sync=0.005 s, total=0.043 s; sync files=3, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=0 kB; lsn=0/1E284B8, redo lsn=0/1E284B8
2025-05-19 23:39:30.909 UTC [5] LOG: database system is ready to accept connections
DETAILS TAB:
Deployment successful
Initialization (00:00)
Pre-deploy (00:34)
Deploy (00:02)
Post-deploy Not started
Postgres Data UI (can't see tables)
A custom interface into your database
(OK) Deployment Online
This service has an active deployment
(OK) Required Variables
This service has all the necessary variables that this UI uses to connect to the database.
(loop not loading) Database Connection
8 Replies
9 months ago
Hey Santiago,
Have you tried connecting with psql or a GUI utility like TablePlus to confirm that you can connect to the database through your TCP Proxy?
Status changed to Awaiting User Response Railway • 9 months ago
echohack
Hey Santiago,Have you tried connecting with psql or a GUI utility like TablePlus to confirm that you can connect to the database through your TCP Proxy?
9 months ago
I've tried using psql DATABASE_PUBLIC_URL:
error: connection to server at "autorack.proxy.rlwy.net" (35.212.52.114), port 48574 failed: server closed the connection unexpectedly
This probably means the server terminated abnormally before or while processing the request.
Status changed to Awaiting Railway Response Railway • 9 months ago
9 months ago
I see, my coworker is noting you have an unusual port on your proxy. Did you mean to use 5432?
Status changed to Awaiting User Response Railway • 9 months ago
echohack
I see, my coworker is noting you have an unusual port on your proxy. Did you mean to use 5432?
9 months ago
Iv'e edited the port on my project env vars (strapi) and after run develop command I've obtained:
KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full.
And using psql:
error: connection to server at "autorack.proxy.rlwy.net" (35.212.52.114), port 5432 failed: Operation timed out
Is the server running on that host and accepting TCP/IP connections?
Status changed to Awaiting Railway Response Railway • 9 months ago
9 months ago
It would be great to be able to export a backup file but I find it impossible...
9 months ago
You should be able to connect via tcp proxy. It's edited on the Settings page of your Service. Once you edit the port you need to redeploy the Postgres Service or else the TCP Proxy will not work.
I'm noticing that it's still misconfigured: autorack.proxy.rlwy.net:48574 -> :2345
Status changed to Awaiting User Response Railway • 9 months ago
echohack
You should be able to connect via tcp proxy. It's edited on the Settings page of your Service. Once you edit the port you need to redeploy the Postgres Service or else the TCP Proxy will not work.I'm noticing that it's still misconfigured: autorack.proxy.rlwy.net:48574 -> :2345
9 months ago
It's always been configured this way since the instance was created.
Status changed to Awaiting Railway Response Railway • 9 months ago
9 months ago
Well, it works now. I just had to delete that TCP config and create a new one.
Status changed to Solved santyas • 9 months ago