You are not logged in.
Pages: 1
deep42thought recently set up a mirror pool: http://pool.mirror.archlinux32.org/
However, many hosts need to update their configurations to properly accept the new vhost.
These are confirmed to work:
32.arlm.tyzoid.com
arch32.mirrors.simplysam.us
ind.mirror.archlinux32.org
jpn.mirror.archlinux32.org
mex.mirror.archlinux32.org
sgp.mirror.archlinux32.org
These are confirmed to not work:
archlinux32.vollzornbrot.de (apache default page)
These work, but need configuration changes:
archlinux32.mirror.roelf.org (Redirects to https://archlinux32.mirror.roelf.org/)
Edit:
Updated to move arch32.mirrors.simplysam.us to the 'working' list.
Edited by deep42thought:
I moved even more mirrors up, removed mirror.archlinux32.org - it's not in the pool.
Last edited by tyzoid (2017-11-23 20:18:58)
Offline
I think I fixed the configuration on archlinux32.mirror.roelf.org. Can somebody verify it works for them?
Offline
I don't want to disable HSTS.
But it forcing https shouldn't be an issue I think, the certificates is valid.
Offline
https://archlinux32.mirror.roelf.org cert is expired
Offline
that's a design problem of pool.mirror.archlinux32.org:
this fqdn resolves to all (active) mirrors of ours, but there is (currently) no mechanism in place to distribute a valid certificate, so most mirrors simply show their default cert ...
we're open to suggestions
Offline
Pages: 1