For the fly.io team:
Just a bug report:
Once we have a pg setup, the hostname.flycast
does not work. We have to use hostname.internal
instead.
Thanks,
Jack
For the fly.io team:
Just a bug report:
Once we have a pg setup, the hostname.flycast
does not work. We have to use hostname.internal
instead.
Thanks,
Jack
If your app is running properly otherwise, you can try running fly pg add_flycast -a <app_name>
to add the service keys to the machine configuration. Might work for you.
Thanks, Mark. Here is what I got:
fly pg add_flycast -a pg-whereis
Error: failed to enable flycast for pg machine 328761e2ad1468 because a service already exists on the postgres port(s)
Interesting. Do you have a private ipv6 allocated to the db? (fly ips list -a pg-whereis
)
VERSION IP TYPE REGION CREATED AT
v6 fdaa:15:38d2:0:1::6 private global Apr 27 2025 15:38