Issue externally connecting to Fly.io database
Hello Waspeteers,
Not perse a Wasp issue, but figured I would try asking as I've been struggling to connect to my Fly.io database from trigger.dev.
I followed this guide, without any luck: https://fly.io/docs/postgres/connecting/connecting-external/
I have set up a shared ipv4 address, but am not sure if this is sufficient. Do i need a dedicated ipv4 address?
I would like my trigger.dev jobs to be able to directly write to my database. It works when developing locally but fails to establish a connection when i deploy it to production.
When i run
To test the Postgres connection I am using psql without any luck too:
When running this psql command I am getting the error:
Does anyone have experience setting this up and willing to help me? Bit stuck here atm.
Thanks!
(I have replaced host/appname with paceholders)
Not perse a Wasp issue, but figured I would try asking as I've been struggling to connect to my Fly.io database from trigger.dev.
I followed this guide, without any luck: https://fly.io/docs/postgres/connecting/connecting-external/
I have set up a shared ipv4 address, but am not sure if this is sufficient. Do i need a dedicated ipv4 address?
I would like my trigger.dev jobs to be able to directly write to my database. It works when developing locally but fails to establish a connection when i deploy it to production.
When i run
fly services list -a my_app_nameTo test the Postgres connection I am using psql without any luck too:
psql "host=my-app-production-db.fly.dev dbname=my_app_db_name user=postgres sslmode=require"When running this psql command I am getting the error:
Does anyone have experience setting this up and willing to help me? Bit stuck here atm.
Thanks!
(I have replaced host/appname with paceholders)
