That was it - looks like our SSL automation forced a redirect to HTTPS. Something else to fix :) Thanks! Travis On Fri, May 21, 2021 at 5:09 AM Fabian Arrotin <arrfab at centos.org> wrote: > On 21/05/2021 05:15, Travis Newton via CentOS-mirror wrote: > > Hi, > > > > Thanks for the advice! I loosened up the firewall after I noticed an > > issue with another project we mirror and that resolved the issue there > > and I thought it might have an effect with CentOS but it appears that's > > not the case. I can rsync with the official CentOS repo for mirrors so I > > think my IP should be fine. I checked the access logs and I'm still > > getting (probably cached) hits to our mirror and the other distros we're > > mirroring are having zero issues. > > > > I'll wait to see what Fabian says. > > > > Thanks again! Cheers, > > > > Avij answered already, so if you have 301/302 redirect to *enforce* > https, the crawler doesn't follow redirect and so can't reach needed > files to verify content > > > -- > Fabian Arrotin > The CentOS Project | https://www.centos.org > gpg key: 17F3B7A1 | twitter: @arrfab > _______________________________________________ > CentOS-mirror mailing list > CentOS-mirror at centos.org > https://lists.centos.org/mailman/listinfo/centos-mirror > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-mirror/attachments/20210521/fe68636c/attachment-0005.html>