# DB Connection issues

**URL:** <https://community.fly.io/t/db-connection-issues/5801>\
**Category:** General\
**Tags:** elixir, postgres\
**Created:** [June 28, 2022, 6:52pm UTC](https://community.fly.io/t/db-connection-issues/5801 "2022-06-28T18:52:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mark](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mark/32/15656_2.png) [@Mark](https://community.fly.io/u/Mark)\
**Post date:** [July 1, 2022, 12:24am UTC](https://community.fly.io/t/db-connection-issues/5801/2 "2022-07-01T00:24:00Z")

</div>

Hi @eliel!

Have you checked on your IPv6 settings for Ecto? They can be set in the Dockerfile using ENV.

> [@Could not contact remote node reason: :nodedown. Aborting...](https://community.fly.io/t/could-not-contact-remote-node-reason-nodedown-aborting/5221/3):
>
> I’m experiencing this issue with my application. ➜ app git:(fly) fly ssh console Connecting to top1.nearest.of.savvycal-staging.internal... complete # app/bin/mighty remote Erlang/OTP 24 [erts-12.1.5] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-threads:1] [jit] Could not contact remote node savvycal-staging@fdaa:0:61d4:a7b:9d36:7c1f:f184:2, reason: :nodedown. Aborting... In the logs: 2022-06-13T16:21:57Z app[7c1ff184] iad [info]Reaped child process with pid: 728, exit code: 0 2022-06-13T…

---

_[View the full topic](https://community.fly.io/t/db-connection-issues/5801)._