fix: change default mysql hostname on new sites from localhost to 127… #1818
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As described on this forum post on the Ghost Forum, having the database hostname set to the current default of
localhost
inconfig.production.json
results in the hostname being resolved to an IPV6 address when connecting to the database in Node 18, as opposed to IPV4 resolution in Node 16.Since the upgrade to Node 18, this issue causes sites created with
ghost install
to throwECONNREFUSED ::1:3306
when trying to start Ghost, as well as to preventghost install
andghost setup
from successfully creating theghost
MySQL user. Though the current workaround of setting the database hostname inconfig.production.json
as127.0.0.1
to force Node to use IPV4 and re-runningghost setup
works fine, I believe it would be better for this to be the new default behavior.I really hope I this little change will be helpful, and thank you for keeping up the great work on Ghost!😌