Can't connect to postgres after moving between organizations

Phoenix
1

I’ve been using wireguard to connect to my postgres instance with psql. I moved my instance between organizations, created a wireguard peer in that organization, disconnected from wireguard, connected to the new peer, and tried psql again, but I’m getting:

psql: error: could not translate host name “winter-night-5547.internal” to address: Name or service not known

2

Actually, I don’t think this is just a vpn problem. My fly app is getting the same error.

3

Apps need a redeploy after they move, which is a little tricky for postgres. It requires a few min of downtime to stop them and then start them up on the new private network.

Do you want me to go ahead and do that for your apps on the new org?

4

The command warned me about that so I assumed it would just happen. It’s down now anyway so do whatever you need to. Is this something I need to contact you to do in the future?

5

I really need to get this working. Is there something you have to do or is it something I should do?

6

You should be good now, sorry for the delay. This should be an automatic process, seems we just had a TODO that to-didn’t.

7

Hi @kurt! I have the same problem. My application can’t connect to the database after moving to the new organization. Is there a way to do this now?

apps:

shy-rain-1653 (elixir app)
brandkit-db-staging (postgres)
8

It seems like the Elixir app didn’t get set to the new network properly. You should be all set now, sorry about that.

1 Like
9

We are evaluating fly.io for a production app. I am experiencing this issue as well, moving a Rails app from one org to another. My rails instance cannot connect to my postgres instance after the move. The error is:

could not translate host name “(redacted).internal” to address: Name or service not known

Things I tried - restarting both instances, resetting wireguard, re-deploying, etc. Any suggestions?

1 Like