Unable to connect to (open) Neon Postgres after assigning egress-ip

Questions / Help
,
1

I have a Node.js app the connects to a Neon Postgres instance. This runs fine, however when I allocate a new egress IP (fly machine egress-ip [command]), I am unable to connect to Postgres.

The Postgres instance is open and has no IP restrictions so im not sure why I am unable to connect.

The core of my .toml file is as follows:

[http_service]
  internal_port = 3000
  force_https = true
  auto_stop_machines = 'off'
  auto_start_machines = false

  [[http_service.checks]]
    interval = '30s'
    timeout = '5s'
    grace_period = '10s'
    method = 'GET'
    path = '/health'

[[vm]]
  size = 'shared-cpu-2x'
  memory = '4gb'
  cpu_kind = 'shared'
  cpus = 2

Can anyone advise why I am unable to connect to Neon Postgres after an outbound IP change?

2

Same here, but for everything. Can’t make a request
Still looking for a solution

Have you solved your issue?

3

No solution as yet. The feature appears to be broken.

See the ongoing discussion here: Static egress IPs for machines - #37 by ben_h

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.