fix(desktop): force IPv4 DNS resolution to prevent IPv6 ETIMEDOUT#1248
Open
DrUmranAli wants to merge 2 commits into
Open
fix(desktop): force IPv4 DNS resolution to prevent IPv6 ETIMEDOUT#1248DrUmranAli wants to merge 2 commits into
DrUmranAli wants to merge 2 commits into
Conversation
Many users on ISPs with misconfigured or incomplete IPv6 routing are experiencing permanent `connect ETIMEDOUT 2600:9000:...` errors when the desktop app attempts to connect to Strava's AWS servers. Because Node.js 17+ defaults to preferring IPv6 over IPv4, the desktop app will attempt to bind to the dead IPv6 address, hang, and timeout instead of falling back to a working IPv4 address. This PR forces the underlying Node.js DNS resolver to prioritize IPv4 globally, which completely eliminates this timeout.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
TIP This summary will be updated as you push new changes. Give us feedback
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Many users on ISPs with misconfigured or incomplete IPv6 routing are experiencing permanent
connect ETIMEDOUT 2600:9000:...errors when the desktop app attempts to connect to Strava's AWS servers.Because Node.js 17+ defaults to preferring IPv6 over IPv4, the desktop app will attempt to bind to the dead IPv6 address, hang, and timeout instead of falling back to a working IPv4 address.
This PR forces the underlying Node.js DNS resolver to prioritize IPv4 globally, which completely eliminates this timeout.