You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/04/10 17:58:25 UTC
[jira] [Resolved] (INFRA-11614) archive.apache.org rejecting
requests from 54.153.17.229
[ https://issues.apache.org/jira/browse/INFRA-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Lambertus resolved INFRA-11614.
-------------------------------------
Resolution: Fixed
I removed the ban yesterday. Your NAT gateway doesn't seem to have been one of the problem-causing IPs, but you shouldn't be using archive.a.o to grab production build artifacts. Please use our mirrors or maven central.
> archive.apache.org rejecting requests from 54.153.17.229
> --------------------------------------------------------
>
> Key: INFRA-11614
> URL: https://issues.apache.org/jira/browse/INFRA-11614
> Project: Infrastructure
> Issue Type: Bug
> Components: HTTP Server
> Reporter: Philip Zeyliger
> Assignee: Chris Lambertus
>
> Hi there,
> We're experiencing connection timeouts to {{archive.apache.org}} from EC2 machines in us-west-1. (An example IP is 54.153.17.229.) We're getting these errors in connection with building some Apache projects from source (like https://github.com/apache/sqoop/blob/branch-1.99.5/dist/pom.xml#L163).
> We're obviously working on redirecting our builds to point at something different, but we'd love to learn definitively that Apache has, in fact, blocked a chunk of EC2, and whether it's possible to lift that block.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)