Hi Luan,
The IPv6 issue does not affect internal communication between Fly machines and MPG - also, if your app and MPG cluster are in iad, they would also be entirely unaffected by problems in sjc.
I see your cluster as healthy here, can you give more details as to what you’re seeing in your app? can you connect to the cluster with fly mpg connect?
(Also, you can reach out for help with your MPG cluster using the “Support” thingy in the Fly.io dashboard)
I see your cluster as healthy here, can you give more details as to what you’re seeing in your app? can you connect to the cluster with fly mpg connect?
Yeah, it’s healthy now, thank you! A couple of minutes after I opened this thread, it came back up. It was down for about 10 minutes.
However, even after the Managed Postgres page was up and running again, the apps still couldn’t connect to the database (I tried restarting the machines). What actually worked was scaling them down to 0 and then back up again. It did work from my personal machine using pgAdmin over the WireGuard tunnel.
I haven’t tried connecting directly with mpg connect, but my apps just couldn’t reach the database, as shown in the screenshot below.
(Also, you can reach out for help with your MPG cluster using the “Support” thingy in the Fly.io dashboard)
Thank you for the tip! To be honest, I got a little scared when I was on the mpg page and it was showing the skeleton loader with no data… After a while, it displayed a message saying “Setting up your cluster”, so I rushed over here to the forum.
Thank you for your help! I hope it won’t happen again, but if it does, I’ll remember to use the support button =)