I am looking at a managed Postgres cluster under my personal organization that is up and running the green glowing dot and everything pooling enabled. It’s even creating a backup. However, when I run ‘fly mpg connect’, I get an error saying there’s no Postgres clusters in my organization.
1 Like
I have the same problem!
CLI version: fly v0.3.110 darwin/arm64
We have three (!) managed Postgres clusters running in the selected organization, all showing green in the dashboard.
Update:
I noticed that with CLI version 0.3.110, there are new commands like list and status. However, none of them are able to detect or interact with the existing Postgres clusters.
A fly wireguard reset might help — it didn’t work for me, but it did solve the issue for a colleague.
What worked for me:
FLY_API_TOKEN=$(fly tokens create org --expiry 1h --org XXX) fly mpg connect
Alternatively, you can manually create an org token and reuse it instead of generating a new one each time. Then pass it like this:
fly mpg list -t fm2_XXXX
Also, according to support, your local Postgres version (psql) should be v16, matching the Fly-managed Postgres version.
What finally worked for me:
fly auth logout
fly auth login
After that, fly mpg list worked even without passing an explicit token.
I assume the CLI token I had previously stored wasn’t valid (or compatible) for interacting with the new Postgres clusters.
2 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.