# Ghost Update: ECONNREFUSED ::1:3306 + Error code 502

**URL:** <https://forum.ghost.org/t/ghost-update-econnrefused-3306-error-code-502/41859>\
**Category:** Developer help\
**Created:** [October 13, 2023, 7:14am UTC](https://forum.ghost.org/t/ghost-update-econnrefused-3306-error-code-502/41859 "2023-10-13T07:14:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![markstos](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/markstos/32/18182_2.png) [@markstos](https://forum.ghost.org/u/markstos)\
**Post date:** [October 13, 2023, 6:50pm UTC](https://forum.ghost.org/t/ghost-update-econnrefused-3306-error-code-502/41859/2 "2023-10-13T18:50:20Z")

</div>

@daniellockyer There are multiple reports recently of the same kind of IPv6 related breakage on what looks like a supported stack.

The other report recently was:

> [@Installation Errors Using Official Doc](https://forum.ghost.org/t/installation-errors-using-official-doc/41691/8):
>
> Thanks again for reply. I am able to login MySQL with the credentials used. Looking at IPV4, doesn’t it default to IPV6?

The trigger seems to be the same: users ran an update of either Ghost or Ubuntu and some connections start defaulting to IPv6 instead of IPv4. In turn, this fails if the right entries aren’t in /etc/hosts.

I’m not sure if:

1. This should be considered a regression, so Ghost should just try to default to IPv4 for now because it doesn’t need an IPv6 connection on localhost.
2. The behavior was intentional and desirable, so the “fix” is update some documentation.

I’m guessing it’s #1, and there’s some place in the Ghost stack where it can be configured to explicitly keep using IPv4 for localhost connections.

---

_[View the full topic](https://forum.ghost.org/t/ghost-update-econnrefused-3306-error-code-502/41859)._