Hello,

We do not impose any outbound connections limits whatsoever, nor do we have that ability, I would have to recommend getting in contact with the 3rd party provider for that issue.

As for the database, It was misconfigured with an HTTP domain instead of a TCP Proxy, I have added the TCP Proxy so please redeploy the database so that setting can take effect.

Best,

Brody

For the DB, I added the TCP proxy previously but removed it. But I'll try it again

Also we tested pulling data from his prod server to our staging environment, and that worked perfectly. It didn't work when pulling from his prod server to our prod environment. There are no constraints at all between how you set up staging and production environments here?

There are no constraints at all between how you set up staging and production environments here?

None what so ever.

Ok thanks. Also, are my prod and staging DBs configured differently? I'm able to connect to the staging DB but not the prod DB. We're following the same format psql postgresql://user:password@proxy_url:port/db_name

staging's url starts with junction.* and prod starts with autorack.*

What error do you get?

psql postgresql://postgres:postgres_pass@proxy_url:port/railway

psql: error: connection to server at "<postgres_url>" (IP_ADDRESS), port PORT failed: server closed the connection unexpectedly

This probably means the server terminated abnormally

before or while processing the request.

Have you redeployed the database since I asked you to?

Ah I forgot to do that, thank you

Working now?

Yes it works thanks! And we found a workaround with the production problem.