This is the result of the flyctl info -a <db-app-name>:
App
Name = <db-app-name>
Owner = <owner>
Platform = machines
Hostname = <db-app-name>.fly.dev
Services
PROTOCOL PORTS FORCE HTTPS
IP Addresses
TYPE ADDRESS REGION CREATED AT
v4 <Ip-v4> global 33s ago
v6 <Ip-v6> global 1m18s ago
P.s. This is new DB created. If i will use the above config to deploy it again. It will crash.
I added this one to get the 12500 port for the postgres instance so i can connect it to Preset.io. Rest of the toml file was generated by this command:
fly config save --app <db-app-name>
All i want is to connect this V2 app to the preset.io.
App
Name = <db-app-name>
Owner = <owner>
Platform = machines
Hostname = <db-app-name>.fly.dev
Services
PROTOCOL PORTS FORCE HTTPS
TCP 12500 => 5432 [] False
TCP 80 => 8080 [HTTP] True
443 => 8080 [TLS,HTTP] False
IP Addresses
TYPE ADDRESS REGION CREATED AT
v4 <IPv4> global 11h38m ago
v6 <IPv6> global 11h39m ago
Feel free to have a browse through all of our Postgres docs, though. It’s not too clear how much basic troubleshooting you’ve done, or if you’re still stuck, but the “Monitoring” and “Connect with flyctl” pages in particular can help you see if your database cluster is healthy and you can connect in the usual ways before adding the external connection bits.