-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API/Gateway listens on both IPv4 and IPv6 #9788
base: master
Are you sure you want to change the base?
Conversation
This LGTM for new installations but existing ones will continue to use the old defaults unless there's a config migration, do you think this should include one? |
I think we should include one. |
Is there a PR with a config migration example that I can take a look at to add that into this PR? |
Yes |
Yup, hopefully I'll be able to get to it sometime this week. |
@Rishi556 : just checking to see if this is something you'll still be able to tackle? |
@BigLep I think so, just have gotten very busy and will continue to be until this weekend, but I might finally have some time after that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am afraid this is blocked by bugs listed in #9637 (comment) – once resolved, we can get back to this PR.
Node.JS 18 stopped reordering DNS to have IPv4 addresses be first(nodejs/node#39987), and this causes some issues since Kubo isn't listening for API requests on [::1]. To fix this, we change the default config to listen on IPv6 and IPv4 for both api and gateway. This PR will resolve #9637.