Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#78001 - New mirror
Attached to Project:
Arch Linux
Opened by Avi H.D (Strykar) - Sunday, 26 March 2023, 15:38 GMT
Last edited by Arun Bahl (pitastrudl) - Tuesday, 27 June 2023, 16:35 GMT
Opened by Avi H.D (Strykar) - Sunday, 26 March 2023, 15:38 GMT
Last edited by Arun Bahl (pitastrudl) - Tuesday, 27 June 2023, 16:35 GMT
|
DetailsMirror domain name:
mirror.4v1.in Geographical location of the mirror: MAH, India (IN) URLs for supported access methods (http(s), rsync) (no ftp): - rsync://mirror.4v1.in/archlinux/ - https://mirror.4v1.in/archlinux - http://mirror.4v1.in/archlinux Your mirror's available bandwidth: 1 Gbit/s, unmetered traffic An administrative contact email (optional, see below) strykar (at) hotmail.com An alternative administrative contact email (optional) --- (tier 1 mirrors) Rsync IPs so your server(s) can be allowed to sync off tier 0 (rsync.archlinux.org) - 182.70.116.80 - No IPv6 atm (tier 2 mirrors) The name of tier 1 mirror you are syncing from. You can find available tier 1 mirrors in https://archlinux.org/mirrors/tier/1/ - rsync://mirror.selfnet.de/archlinux/ Server: - Archlinux - 250 GB SSD - Nginx /with QUIC |
This task depends upon
Currently it seems that the https link is not working. For now i'll add both except the https one. Let us know once https is available again.
I had to poke around the ISP router to get DHCPv6-PD working, took me a week, but the hostname resolves to an IPv6 address too now.
I suspect it was this period where the HTTPS traffic was just routed over IPv6 and it made the service appear to be down.
In any case, both issues should be fixed now, I just tested all 3 protocols appear fine to remote hosts.