Hello,
we had to rebuild our mirror server (known as ftp.plusline.de before) and
it is now available at new IP addresses.
HTTP: http://ftp.plusline.net/centos/
HTTPS: https://ftp.plusline.net/centos/
RSYNC: rsync://ftp.plusline.net/CentOS/
Sync schedule: Every 6 hrs
Bandwidth: 1000 Mbps
Location: DE, Frankfurt
Sponsor: Plus.line AG
Sponsor URL: https://www.plusline.net
IPv4 address to authorize: 82.98.66.54
IPv6 address to authorize: 2a02:2e0:414:102:d::54
Email contact: ftp-admin(a)plusline.net
Mirroring AltArch : no
Kind regards
Jan
We marked FTP as deprecated on the CreatePublicMirrors wiki page in
December, and now it's time to move to the next step in getting rid of
FTP. Setting up firewall rules for FTP is an unneeded headache for both
mirror operators and clients, and establishing connections to FTP sites
is slower than establishing connections to HTTP sites.
I have a neat script that sends notifications to mirror operators if it
detects problems with mirrors. Some of you may have seen such emails.
The email has also included information about nonworking FTP URLs. From
now on, however, the script will silently remove any nonworking FTP URLs
from the database if the FTP URL has been unreachable for 8 days (the
default threshold for notifications), instead of sending a nag email to
the mirror operator. If your FTP URL has disappeared from
https://www.centos.org/download/mirrors/ , this is the reason.
We will eventually remove all FTP URLs from the mirror database and stop
including FTP URLs in the output of mirrorlist.centos.org. The blockers
here are the few mirrors that only have an FTP URL listed (no HTTP). Two
of them seem to actually have their mirror available over HTTP as well,
but the HTTP URL is not listed in our database. I've sent an email to
them last week asking if it's OK to add their HTTP URL, and I've also
sent an email to the other FTP mirrors asking if they could make their
mirror available over HTTP. Once these issues been resolved (or a
sufficient amount of time has passed) we can drop the FTP URLs from our
database.
You are still of course free to serve the files over FTP if you wish,
but there won't be any links to your FTP site from centos.org.
Thanks for your cooperation!
Hey,
I'm going to be discontinuing the server that mirrors.gpmidi.net is hosted
on in the next few weeks. How long should I leave it up once it's removed
from rotation? I'm not in a huge rush; a week or two is fine.
-Paulson McIntyre
Dear CentOS mirror admin,
I found that our mirror was not shown in Hong Kong of CentOS mirror list
since 12-13 Jun 2018, may I know anything wrong on our mirror server? I
checked our mirror did not down and keeps updating.
Our mirror address is http://centos.nethub.com.hk/
Ming
Could I request that 46.43.57.39 & 46.43.57.33 are added to the
upstream mirror ACL for the main centos repo please?
Regards
Chris
--
Chris Cottam Bytemark Hosting Support
http://www.bytemark.co.uk/
tel: +44 (0) 1904 890 890
So let's get this straight..
There are a few CentOS mirrors that redirect their http traffic to
https. This is fairly easy nowadays with Let's Encrypt and their
automatic cert installation scripts. While I believe that the intention
is good, I'm afraid the forced redirects are not actually helping.
I can't speak for other projects, but for CentOS mirrors, I believe that
you should respond using the same protocol the request was sent. My
concern is that there are organizations (hospitals, banks, research
centers etc) that want to make sure no confidential information leaks
out from their organization. Connections to random HTTPS sites may get
blocked at their firewall because the firewall can't see what's inside
the request.
It should also be pointed out that the scripts behind
http://mirror-status.centos.org/ will (currently) happily follow all
kinds of redirects to retrieve the timestamp file. However, the scripts
that create the actual data for mirrorlist.centos.org for each
repository are unable to access https URLs. So the moment you set up
that redirect to https, your mirror stopped being included in the output
of mirrorlist.centos.org.
I have already tried reaching out to a few mirrors doing such redirects,
but I have not received a response yet. Those mirrors will eventually be
disabled after a few more automatic nag emails, but I'm hoping that
those mirror operators would exclude their CentOS mirror traffic from
the redirects before that happens.
To be clear, you are free to offer CentOS files over https, but the
redirects should be disabled. I can see the CentOS mirror system
supporting https and mirrorlist.c.o (optionally) handing out https URLs
some day, but even then, I believe that http requests should be answered
with http, and https requests should be answered with https.
Thank you for your time!