Маврин Михаил 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.