@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:
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:
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.
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.
The question is whether it should also be a breaking change for Ghost, or whether Ghost should smooth over the difference.
I imagine nearly everyone connecting from Ghost to MySQL via a “localhost” lookup supports IPv4 lookups and and likely already using IPv4 resolution.
For the less common case with remote databases, I’m less sure what’s ideal.
There are probably a lot more domains that have IPv4 resolution setup but not IPv6, then the other way around.
This is a place where some telemetry would be useful, to better understand how many sites break Ghost forced the resolution back to IPv4 for all DNS lookups for now. I expect it may fix more than it would break.
This should be a long term fix, assuming major distro updates don’t override your hosts (you have to explicitly perform a major distro upgrade, and explicitly tell the upgrade utility to pick the distro-suggested version over your own)