You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to reach repo.jenkins-ci.org from a pure IPv6 environment
Reproduction steps
# host repo.jenkins-ci.org
repo.jenkins-ci.org is an alias for jenkinsci.jfrog.org.
jenkinsci.jfrog.org is an alias for endpointdns-prod-4-use1-lb.jfrog.io.
endpointdns-prod-4-use1-lb.jfrog.io is an alias for k8s-jfrogsaa-jfrogsaa-d1715df99e-93aeed5af6b09f0b.elb.us-east-1.amazonaws.com.
k8s-jfrogsaa-jfrogsaa-d1715df99e-93aeed5af6b09f0b.elb.us-east-1.amazonaws.com has address 52.22.177.50
k8s-jfrogsaa-jfrogsaa-d1715df99e-93aeed5af6b09f0b.elb.us-east-1.amazonaws.com has address 44.209.124.32
k8s-jfrogsaa-jfrogsaa-d1715df99e-93aeed5af6b09f0b.elb.us-east-1.amazonaws.com has address 34.225.228.28
The text was updated successfully, but these errors were encountered:
I wanted to provide you with an update regarding your recent inquiry about IPv6 support in our cloud servers.
After consulting with our Production Engineering team, I regret to inform you that our current cloud infrastructure does not support IPv6. We are operating exclusively on IPv4, and all network configurations and services are tailored to this protocol.
I've asked them how do they handle Indian users from IPv6-only ISPs (ref. https://dot.gov.in/ipv6-transition), but for now there is nothing the Jenkins infra can do about this (hosting a IPv6 <-> Ipv4 gateway even restricted to repo.jenkins-ci.org would costs us 1000s of bucks per months for the bandwidth alas).
Service(s)
Artifactory
Summary
Unable to reach repo.jenkins-ci.org from a pure IPv6 environment
Reproduction steps
The text was updated successfully, but these errors were encountered: