Arch Linux

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!
Tasklist

FS#46513 - {mirror} Mirror Registration Update

Attached to Project: Arch Linux
Opened by Atlantic.Net Network Operations (atlnet-noc) - Thursday, 01 October 2015, 17:07 GMT
Last edited by Florian Pritz (bluewind) - Friday, 20 May 2016, 17:55 GMT
Task Type Feature Request
Category Mirrors
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Request to update mirror FQDN links and registration details.

Original Request ID: 44973
Current Listing: https://www.archlinux.org/mirrors/atlantic.net/


-----
New Mirroring Information
-----
Mirror domain name : atlantic.net

Geographical location of the mirror (country): USA, Orlando, Florida

URLs for supported access methods (http(s), rsync) (no ftp)
http://mirror.atlantic.net/archlinux/
ftp://mirror.atlantic.net/archlinux/
rsync://mirror.atlantic.net/archlinux/

Your mirror's available bandwidth: 2GB
IPv4 Available: Yes
IPv6 Available: Yes

An administrative contact email: mirror@atlantic.net
An alternative administrative contact email (optional): noc@atlantic.net

(tier 2 mirrors) The name of tier 1 mirror you are syncing from:
mirror.us.leaseweb.net/archlinux/
mirrors.kernel.org/archlinux/

Update Interval: every 4 hours

This task depends upon

Closed by  Florian Pritz (bluewind)
Friday, 20 May 2016, 17:55 GMT
Reason for closing:  No response
Comment by Florian Pritz (bluewind) - Friday, 02 October 2015, 08:56 GMT
You have a rule in HTTPS everywhere that prevents users with that addon from accessing your mirror because the mirror does not provider https service. You might want to look into fixing that. I don't care if you fix it, just wanted to point it out.

Apart from this issue I've updated our DB. Thanks for the nice list.
Comment by Atlantic.Net Network Operations (atlnet-noc) - Friday, 02 October 2015, 14:52 GMT
I am working on getting the HTTP(s) certificate implemented today. Hopefully will have IPv4 and IPv6 HTTP(s) working soon.
Comment by Florian Pritz (bluewind) - Friday, 15 January 2016, 10:13 GMT
What's the status of https?

Loading...