The last major component of the postmarketOS infrastructure is being moved to a new host. This runs mirror.postmarketos.org, build.postmarketos.org and pkgs.postmarketos.org. Some downtime is expected during this migration.
Resolved - The DNS record is fixed, it will take up to 12 hours for the change to update on all DNS providers.
The DNS zone for postmarketos.org is migrate to a new host. The CNAME record for cast.postmarketos.org is pointing to the wrong server.
IPv6 connectivity has been enabled on all the postmarketOS services now. This might cause outages if your traffic is suddenly routed over other protocols or one of the services isn’t listening on IPv6
Monitoring - Looks like the wiki is fully working, even the mobile view. (Aug 07, 2020 - 16:31)
Disrupted - Base wiki is up again, now resolving issues with outdated extensions. (Aug 07, 2020 - 16:09)
The wiki is being migrated to another server and has to be upgraded to the latest release to be able to run on PHP 7.3, due to it being mediawiki this upgrade will take a long while.
Resolved - nameserver move is done, everything seems up again.
The domain name postmarketos.org is being moved between registrars and this is causing some issues with nameservers. The issues should resolve itself in an hour.
Resolved - Server upgrade was successful
vps4.bramix.nl will be put in maintenance mode for a few minutes for upgrading the disk. During this time the major downtime will be that the wiki will be down and the build server won’t be processing hooks.
Resolved - It turns out to be an caching issue with the SSL certificates in the backend, causing hosting 4 to have an older certificate than hosting 5. Currently the IPv4 traffic is routed through an DigitalOcean floating IP which sends traffic to hosting 5 and redirecting to hosting 4 when there’s an issue. Since DigitalOcean doesn’t have a floating IP feature for IPv6 and hosting 5 currently isn’t in an IPv6 region those requests are allways served by hosting 4. The certificate on hosting 4 was up to date but HAProxy wasn’t reloaded when the certificates were refreshed causing it to serve pages on IPv6 with an old certificate.
Investigating - Reports are coming in that for some users the certificate has expired and for some users everything works fine.