{
  "is": "issue",
  "title": "IPv6 certificate issue on postmarketos.org",
  "body": "\u003cp\u003e\u003cem\u003eResolved\u003c/em\u003e -\nIt 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.\nCurrently the IPv4 traffic is routed through an DigitalOcean floating IP which sends traffic to hosting 5 and redirecting to hosting 4 when there\u0026rsquo;s an issue.\nSince DigitalOcean doesn\u0026rsquo;t have a floating IP feature for IPv6 and hosting 5 currently isn\u0026rsquo;t in an IPv6 region those requests are allways served by hosting 4.\nThe certificate on hosting 4 was up to date but HAProxy wasn\u0026rsquo;t reloaded when the certificates were refreshed causing it to serve pages on IPv6 with an old certificate.\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e -\nReports are coming in that for some users the certificate has expired and for some users everything works fine.\u003c/p\u003e\n",
  "createdAt": "2018-11-22 00:00:00 +0000 UTC",
  "lastMod": "2026-01-16 10:39:20 -0800 -0800",
  "permalink": "https://status.nura.eco/issues/ipv6-certificate-postmarketos.org/",
  "severity": "disrupted",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2018-11-22 00:05:00",
  "affected": ["Website"],
  "filename": "ipv6-certificate-postmarketos.org.md"
}