Database stuck on "Database connection"

[rare fox]

After hitting a billing limit, my deployments where gone. So, I've restored them and now the database can't connect to anything. It's showing this log

2025-08-22 13:36:50.343 UTC [6] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-08-22 13:36:50.343 UTC [6] LOG:  listening on IPv6 address "::", port 5432
2025-08-22 13:36:50.349 UTC [6] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-08-22 13:36:50.359 UTC [29] LOG:  database system was interrupted; last known up at 2025-08-22 13:35:13 UTC
2025-08-22 13:36:50.421 UTC [29] LOG:  database system was not properly shut down; automatic recovery in progress
2025-08-22 13:36:50.426 UTC [29] LOG:  redo starts at 0/1CF4E548
2025-08-22 13:36:50.426 UTC [29] LOG:  invalid record length at 0/1CF4E580: expected at least 24, got 0
2025-08-22 13:36:50.426 UTC [29] LOG:  redo done at 0/1CF4E548 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-08-22 13:36:50.433 UTC [27] LOG:  checkpoint starting: end-of-recovery immediate wait
2025-08-22 13:36:50.462 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.008 s, sync=0.005 s, total=0.035 s; sync files=2, longest=0.003 s, average=0.003 s; distance=0 kB, estimate=0 kB; lsn=0/1CF4E580, redo lsn=0/1CF4E580
2025-08-22 13:36:50.470 UTC [6] LOG:  database system is ready to accept connections

Project ID: be3f2db8-13c1-4dfb-b758-fbaace10701c

[rare fox]

Is there any update on this? I really need this deploy to be restored

[untold harbor]

I'm sorry but I'm not seeing any issues from those logs, can you provide any errors you are seeing?

[rare fox]

There are no errors showing, but I can't connect to the database

And this is stuck

[untold harbor]

You don't have a TCP Proxy, that is something the data tab requires.

Note, the database would still be accessible over the private network.

[rare fox]

Ok, nevermind. Turns out after the restart the server that connects to the database via private network couldn't connect properly - maybe it started before the database or something, but it worked after a restart

[untold harbor]

!s