Skip to content

fix: use proxy-local.dfinity.network#10424

Draft
basvandijk wants to merge 1 commit into
masterfrom
basvandijk/proxy-local
Draft

fix: use proxy-local.dfinity.network#10424
basvandijk wants to merge 1 commit into
masterfrom
basvandijk/proxy-local

Conversation

@basvandijk

@basvandijk basvandijk commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

A new domain besides proxy-global.dfinity.networkhas been introduced called proxy-local.dfinity.network which points to the link local fe80::2 IPv6 address. Then in each DC where we have Farm hosts (fr1, dm1, zh1) we have one of the dc_http_proxy nginx servers listen on that link local fe80::2 address. Then this commit repoints the URL to download images from from proxy-global.dfinity.network to proxy-local.dfinity.network. This will mean that when an IC node downloads an image it will always go to a local dc_http_proxy nginx server instead of hopping over the Atlantic. It could still mean that the local nginx has to hop over the Atlantic to download the image from its source but we avoid the double Atlantic transfers that have been causing flakiness.

@basvandijk basvandijk added the CI_ALL_BAZEL_TARGETS Runs all bazel targets label Jun 9, 2026
@github-actions github-actions Bot added the fix label Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI_ALL_BAZEL_TARGETS Runs all bazel targets fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant