Error failed to launch VM: nats: no responders available for request

@dangra is there a reason that deploying the configuration Production - Highly available, 2x shared CPUs, 4GB RAM, 40GB disk in EWR continues to only result in one healthy instance?

I tried again this morning to create this cluster (I’m working on creating repeatable scripts for my infra, so I want to make sure this is consistent), and I still only have one instance healthy:

❯ fly checks list -a flxwebsites-db
Health Checks for flxwebsites-db
  NAME | STATUS   | MACHINE        | LAST UPDATED | OUTPUT
-------*----------*----------------*--------------*--------------------------------------------------------------------------
  pg   | passing  | 0e286961b50867 | 4m36s ago    | [✓] transactions: read/write (341.43µs)
       |          |                |              | [✓] connections: 9 used, 3 reserved, 300 max (4.39ms)
-------*----------*----------------*--------------*--------------------------------------------------------------------------
  role | passing  | 0e286961b50867 | 4m37s ago    | leader
-------*----------*----------------*--------------*--------------------------------------------------------------------------
  vm   | passing  | 0e286961b50867 | 5m3s ago     | [✓] checkDisk: 37.06 GB (94.7%) free space on /data/ (86.66µs)
       |          |                |              | [✓] checkLoad: load averages: 0.00 0.00 0.00 (181.59µs)
       |          |                |              | [✓] memory: system spent 0s of the last 60s waiting on memory (96.84µs)
       |          |                |              | [✓] cpu: system spent 0s of the last 60s waiting on cpu (82.71µs)
       |          |                |              | [✓] io: system spent 0s of the last 60s waiting on io (73.62µs)
-------*----------*----------------*--------------*--------------------------------------------------------------------------
  pg   | critical | 21781e67a03896 | 4m43s ago    | 500 Internal Server Error
       |          |                |              | failed to connect to proxy: context deadline exceeded
-------*----------*----------------*--------------*--------------------------------------------------------------------------
  role | critical | 21781e67a03896 | 4m32s ago    | 500 Internal Server Error
       |          |                |              | failed to connect to local node: context deadline exceeded
-------*----------*----------------*--------------*--------------------------------------------------------------------------
  vm   | passing  | 21781e67a03896 | 3m57s ago    | [✓] checkDisk: 37.06 GB (94.7%) free space on /data/ (67.84µs)
       |          |                |              | [✓] checkLoad: load averages: 0.00 0.00 0.00 (68.78µs)
       |          |                |              | [✓] memory: system spent 0s of the last 60s waiting on memory (79.78µs)
       |          |                |              | [✓] cpu: system spent 144ms of the last 60s waiting on cpu (31.2µs)
       |          |                |              | [✓] io: system spent 384ms of the last 60s waiting on io (22.64µs)
-------*----------*----------------*--------------*--------------------------------------------------------------------------