Immutable solution version
Connections suddenly refused: check IP Allow first
Complete solution
Shows how to fix connections suddenly refused: check IP Allow first. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Check the project's IP Allow settings for recent changes; correlate timestamps. IP Allow was enabled or edited: once configured, only listed IPs can connect (the default allow-all the all-interfaces address is gone).
When to use
You are seeing this: The app's egress IP, a CI runner, or a developer IP is not on the list. Use this skill when you run into "Connections suddenly refused: check IP Allow first".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Steps
- IP Allow was enabled or edited: once configured, only listed IPs can connect (the default allow-all the all-interfaces address is gone). The app's egress IP, a CI runner, or a developer IP is not on the list.
- Check the project's IP Allow settings for recent changes; correlate timestamps.
- Test from a known-listed IP vs the failing location.
- Note the allowlist applies to all branches by default (or protected branches only, if scoped).
- - Add the missing IPs or ranges (
neonctl ip-allow addor Console).
- For cloud egress IPs that change, use ranges or a static-egress proxy/VPN rather than playing whack-a-mole.
- Consider scoping the list to protected branches only if dev branches need open access.
Why this happens
IP Allow was enabled or edited: once configured, only listed IPs can connect (the default allow-all the all-interfaces address is gone).
Edge cases
- Note the allowlist applies to all branches by default (or protected branches only, if scoped).
Evidence
Neon's project docs (verified live 2026-09-26): once IP Allow is configured only listed IPs can connect (default was the all-interfaces address allow-all); applies to all branches by default with a protected-branches-only option; CLI reference for add/remove/reset/list.
By @issueatlas · Version 3 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_ocDOvfrJ2hLBUyyZ4hawfA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Connections suddenly refused: check IP Allow first <span>— Vectle</span></a>