Hi!
I'd like to add another mirror to the list. Please find the information below:
HTTP: http://mirrors.datahouse.ru/centos/ HTTPS: https://mirrors.datahouse.ru/centos/
Sync schedule: Every 3 hrs Bandwidth: 2 Gbps Location:Russia, Moscow Sponsor: filanco.ru Sponsor URL: https://filanco.ru/ IPv4 address to authorize: (185.229.9.20) Mirroring AltArch: No
Thanks! Please let me know if I missed anything.
Маврин Михаил kirjoitti 19.7.2019 klo 13.47:
Hi!
I'd like to add another mirror to the list. Please find the information below:
HTTP: http://mirrors.datahouse.ru/centos/ HTTPS: https://mirrors.datahouse.ru/centos/
Sync schedule: Every 3 hrs Bandwidth: 2 Gbps Location:Russia, Moscow Sponsor: filanco.ru Sponsor URL: https://filanco.ru/ IPv4 address to authorize: (185.229.9.20) Mirroring AltArch: No
Thanks! Please let me know if I missed anything.
Hi, I'm afraid there are some issues that will need to be fixed before this mirror can be added.
My mirror checking script reports this:
repomd.xml failed at http://mirrors.datahouse.ru/centos/6/extras/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/6/contrib/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/7/cr/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/7/extras/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/7/fasttrack/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/7/os/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable
Maybe some sort of a rate limiting thing? If my mirror checking script reports errors, it is very likely that users of your mirror would run into these rate limit issues as well.
Also, https://mirrors.datahouse.ru/centos/ does not seem to work at all. It looks like the server is listening on port 443, but it is configured to speak HTTP instead of HTTPS. https://www.ssllabs.com/ssltest/analyze.html?d=mirrors.datahouse.ru is a useful resource to check if everything is OK.
Clicking a few links is unlikely to trigger any request rate limitations. Here's a reproducer and results:
for i in {1..100}; do curl -v http://mirrors.datahouse.ru/centos/6/extras/x86_64/repodata/repomd.xml; done 2>&1 | grep "< HTTP" | sort | uniq -c
33 < HTTP/1.1 200 OK 67 < HTTP/1.1 503 Service Temporarily Unavailable
For https:
$ curl -v https://mirrors.datahouse.ru/centos/timestamp.txt * About to connect() to mirrors.datahouse.ru port 443 (#0) * Trying 185.229.9.20... * Connected to mirrors.datahouse.ru (185.229.9.20) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * NSS error -12263 (SSL_ERROR_RX_RECORD_TOO_LONG) * SSL received a record that exceeded the maximum permissible length. * Closing connection 0 curl: (35) SSL received a record that exceeded the maximum permissible length.
The above error message does not really say that the server is talking http on https port, but this one maybe clarifies that the server is using http on the https port:
$ curl http://mirrors.datahouse.ru:443/centos/timestamp.txt <html> <head><title>404 Not Found</title></head> <body> <center><h1>404 Not Found</h1></center> <hr><center>nginx</center> </body> </html>
The error message should have been something along the lines of "you're speaking plain HTTP to an SSL-enabled server port", not a 404.
Mirror.Truenetwork Team kirjoitti 21.7.2019 klo 13.00:
Hello Anssi Johansson, checked links open without problems Best regards, Eugene 21.07.2019, 02:48, "Anssi Johansson" avij@centosproject.org:
Маврин Михаил kirjoitti 19.7.2019 klo 13.47: Hi! I'd like to add another mirror to the list. Please find the information below: HTTP: http://mirrors.datahouse.ru/centos/ HTTPS: https://mirrors.datahouse.ru/centos/ Sync schedule: Every 3 hrs Bandwidth: 2 Gbps Location:Russia, Moscow Sponsor: filanco.ru Sponsor URL: https://filanco.ru/ IPv4 address to authorize: (185.229.9.20) Mirroring AltArch: No Thanks! Please let me know if I missed anything. Hi, I'm afraid there are some issues that will need to be fixed before this mirror can be added. My mirror checking script reports this: repomd.xml failed at http://mirrors.datahouse.ru/centos/6/extras/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/6/contrib/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/7/cr/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/7/extras/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/7/fasttrack/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable repomd.xml failed at http://mirrors.datahouse.ru/centos/7/os/x86_64/repodata/repomd.xml : 503 Service Temporarily Unavailable Maybe some sort of a rate limiting thing? If my mirror checking script reports errors, it is very likely that users of your mirror would run into these rate limit issues as well. Also, https://mirrors.datahouse.ru/centos/ does not seem to work at all. It looks like the server is listening on port 443, but it is configured to speak HTTP instead of HTTPS. https://www.ssllabs.com/ssltest/analyze.html?d=mirrors.datahouse.ru is a useful resource to check if everything is OK. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org <mailto:CentOS-mirror@centos.org> https://lists.centos.org/mailman/listinfo/centos-mirror
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
-
Anssi Johansson -
Mirror.Truenetwork Team -
Маврин Михаил