HTTP: http://mirror.hkt.cc/centos/ HTTPS: https://mirror.hkt.cc/centos/ Sync schedule: Every 6 hrs Bandwidth: Location: Hong Kong Sponsor: Forewin Telecom Group LTD Sponsor URL: http://www.hkt.cc IPv4 address to authorize: 115.126.83.2 Email contact: mirror@hkt.cc Mirroring AltArch: no
HTTP: http://mirror.friedlmaier.net/centos/ HTTPS: https://mirror.friedlmaier.net/centos/ RSYNC: rsync://mirror.friedlmaier.net/centos/
Sync schedule: Every 3 hrs Bandwidth: Location: Germany / DE Sponsor: Daniel Friedlmaier Sponsor URL: www.friedlmaier.net IPv4 address to authorize: 176.9.169.138 IPv6 address to authorize: 2a01:4f8:151:449b::3 Email contact: daniel@friedlmaier.net Mirroring AltArch: no
On 23/10/2019 15:40, Daniel Friedlmaier wrote:
HTTP: http://mirror.friedlmaier.net/centos/ HTTPS: https://mirror.friedlmaier.net/centos/ RSYNC: rsync://mirror.friedlmaier.net/centos/
Sync schedule: Every 3 hrs Bandwidth: Location: Germany / DE Sponsor: Daniel Friedlmaier Sponsor URL: www.friedlmaier.net IPv4 address to authorize: 176.9.169.138 IPv6 address to authorize: 2a01:4f8:151:449b::3 Email contact: daniel@friedlmaier.net Mirroring AltArch: no
Can you verify that your mirror is reachable ? Our pre-flight script couldn't connect, neither over ipv4 or ipv6 and I then tested from US and EU countries and same result (not even icmp is working now).
Let us know when it will be reachable so that we can validate it and proceed.
Thanks
Hi Fabian,
sorry, my fault! Please try again.
Best regards,
Daniel
On Wed, 2019-10-23 at 16:47 +0200, Fabian Arrotin wrote:
On 23/10/2019 15:40, Daniel Friedlmaier wrote:
HTTP: http://mirror.friedlmaier.net/centos/
HTTPS: https://mirror.friedlmaier.net/centos/
RSYNC: rsync://mirror.friedlmaier.net/centos/
Sync schedule: Every 3 hrs
Bandwidth:
Location: Germany / DE
Sponsor: Daniel Friedlmaier
Sponsor URL: www.friedlmaier.nethttp://www.friedlmaier.net
IPv4 address to authorize: 176.9.169.138
IPv6 address to authorize: 2a01:4f8:151:449b::3
Email contact: daniel@friedlmaier.netmailto:daniel@friedlmaier.net
Mirroring AltArch: no
Can you verify that your mirror is reachable ? Our pre-flight script
couldn't connect, neither over ipv4 or ipv6 and I then tested from US
and EU countries and same result (not even icmp is working now).
Let us know when it will be reachable so that we can validate it and
proceed.
Thanks
_______________________________________________
CentOS-mirror mailing list
CentOS-mirror@centos.orgmailto:CentOS-mirror@centos.org
On 23/10/2019 17:28, Daniel Friedlmaier wrote:
Hi Fabian,
sorry, my fault! Please try again.
Best regards,
Daniel
Still not working : you have AAAA record but ipv6 is blocked ?
curl -6 http://mirror.friedlmaier.net/centos/ (and our mirror crawler connects to both ipv4 and ipv6 if A/AAAA exist)
Hi Fabian,
please try again, DNS problem solved.
Thx and best regards
Daniel
On Wed, 2019-10-23 at 17:51 +0200, Fabian Arrotin wrote:
On 23/10/2019 17:28, Daniel Friedlmaier wrote:
Hi Fabian,
sorry, my fault! Please try again.
Best regards,
Daniel
Still not working : you have AAAA record but ipv6 is blocked ?
curl -6 http://mirror.friedlmaier.net/centos/ (and our mirror crawler
connects to both ipv4 and ipv6 if A/AAAA exist)
_______________________________________________
CentOS-mirror mailing list
CentOS-mirror@centos.orgmailto:CentOS-mirror@centos.org
On 23/10/2019 09:50, mirror mirror wrote:
HTTP: http://mirror.hkt.cc/centos/ HTTPS: https://mirror.hkt.cc/centos/%C2%A0 Sync schedule: Every 6 hrs Bandwidth: Location: Hong Kong Sponsor: Forewin Telecom Group LTD Sponsor URL: http://www.hkt.cc IPv4 address to authorize: 115.126.83.2 Email contact: mirror@hkt.cc Mirroring AltArch: no
Thanks !
Your mirror http://mirror.hkt.cc/centos/ has been added to the mirrors DB It will be listed as a public mirror (and on https://mirror-status.centos.org / https://www.centos.org/download/mirrors/ ) in the following minutes/hours. Your IP address[es] (115.126.83.2 ) has/have been added in the ACL and so you should be able to rsync from msync.centos.org in the next ~10min
Kind Regards,