Can't create PostgeSQL databsae

Hello guys, I have problem with creating database.
I am trying to create database with this command: flyctl postgres create
it should return something like this:

Creating postgres cluster dvdrental in organization personal
Creating app...
Setting secrets...
Provisioning 1 of 1 machines with image flyio/postgres:14.4
Waiting for machine to start...
Machine d5683461b138e9 is created
==> Monitoring health checks  
    Waiting for d5683461b138e9 to become healthy (started, 3/3) Postgres cluster dvdrental created  
Username:    postgres  
Password:    <password>
Hostname:    dvdrental.internal  
Proxy port:  5432  
Postgres port:  5433
Save your credentials in a secure place -- you won't be able to see them again! Connect to postgres
Any app within the Andreas Chandra organization can connect to this Postgres using the following credentials:
For example: postgres://postgres:<password>@dvdrental.internal:5432  Now that you've set up postgres, here's what you need to understand: https://fly.io/docs/reference/postgres-whats-next/

but instead it gave me this error:

Error failed to launch VM: Post "http://[fdaa:0:e212::3]:4280/v1/apps/smart-brain/machines": connect tcp [fdaa:0:e212::3]:4280: operation timed out

I had similar issue few weeks later, but it was as said to me, because server was down:

but now here :

I see that everything is working with no problem, so what is issue here?
Can someone help me with it?

Can you run fly doctor and show the output?

That sounds more like an issue connecting to our API (we have an API that lives only on the wireguard network).

It gave me this output:

Testing authentication token... PASSED
Testing flyctl agent... PASSED
Testing local Docker instance... Nope
Pinging WireGuard gateway (give us a sec)... FAILED
(Error: ping gateway: no response from gateway received)

We can't establish connectivity with WireGuard for your personal organization.

WireGuard runs on 51820/udp, which your local network may block.

If this is the first time you've ever used 'flyctl' on this machine, you
can try running 'flyctl doctor' again.

If this was working before, you can ask 'flyctl' to create a new peer for
you by running 'flyctl wireguard reset'.

If your network might be blocking UDP, you can run 'flyctl wireguard websockets enable',
followed by 'flyctl agent restart', and we'll run WireGuard over HTTPS.

That looks like a WireGuard connectivity issue.

The output suggests a few solutions, can you try them one by one and see if things improve. Running fly doctor again will tell you if things improve.

1 Like

I run flyctl wireguard reset, than:

flyctl wireguard websockets enable
flyctl agent restart
fly doctor again ,but it gave same error…

 fly doctor
Testing authentication token... PASSED
Testing flyctl agent... PASSED
Testing local Docker instance... Nope
Pinging WireGuard gateway (give us a sec)... FAILED
(Error: ping gateway: no response from gateway received)

We can't establish connectivity with WireGuard for your personal organization.

WireGuard runs on 51820/udp, which your local network may block.

If this is the first time you've ever used 'flyctl' on this machine, you
can try running 'flyctl doctor' again.

If this was working before, you can ask 'flyctl' to create a new peer for
you by running 'flyctl wireguard reset'.

If your network might be blocking UDP, you can run 'flyctl wireguard websockets enable',
followed by 'flyctl agent restart', and we'll run WireGuard over HTTPS.

Everything looks good on our end. I looked at the gateway you’re connecting to and your peer is there and everything. Never handshook which means you can’t connect to it.

Can you try a native WireGuard client? On macos there’s an official WireGuard app, on linux I think that’s usually supported by whatever network manager you’d be using.

Anyway, if all else fails, you can try fly postgres create --nomad to use the old API that’s not behind WireGuard. This will create a “v1” postgres cluster. It’s not ideal, but at least it will get you going.

So I was using WSL2 on windows ubuntu trminal.
I just installed Fly.io on windows through power-shell , sign in and run
flyctl doctor, it gave me this output everything is working,right?

flyctl doctor
Testing authentication token... ←[0;32mPASSED
←[0mTesting flyctl agent... ←[0;32mPASSED
←[0mTesting local Docker instance... Nope
Pinging WireGuard gateway (give us a sec)... ←[0;32mPASSED
←[0mNo app provided; skipping app specific checks

so Problem is with WSL2 as I understand?

Oh, yes. I don’t think it works quite right on WSL.

Thanks for help.I will continue on power-shell :slight_smile: