On Tue, Feb 20, 2018 at 02:18:38PM -0700, Erinn Looney-Triggs wrote:
> Will be located at mirror.colorado.edu, only EPEL is planned for now.
>
> We are located in the US, IP address is 128.138.184.3, 1g link speed,
> will be contacting a tier 1 mirror, though honestly we might be a good
> candidate for that as well.

Your mirrormanager entry almost looks correct. The only problem is that
our crawler cannot connect to your mirror. In fact, I have problems
connecting to your mirror from multiple locations, with multiple
different errors:

$ curl https://mirror.colorado.edu/fedora/epel/ -v

either this:

* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to mirror.colorado.edu:443
* stopped the pause stream!
* Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to mirror.colorado.edu:443

or:

* About to connect() to mirror.colorado.edu port 443 (#0)
*   Trying 128.138.184.3... Connection timed out
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host

or:

* About to connect() to mirror.colorado.edu port 443 (#0)
*   Trying 128.138.184.3...
* Connected to mirror.colorado.edu (128.138.184.3) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* NSS error -5961 (PR_CONNECT_RESET_ERROR)
* TCP connection reset by peer
* Closing connection 0
curl: (35) TCP connection reset by peer

So all kind of different errors, which make it impossible for our crawler to
connect to your mirror.

I would also be great if you could offer rsync access as that makes the
crawler so much more efficient.

                Adrian