Fix invalid status.s.o certificate
I don't know if it's redundant or not with the parent task (which references that domain twice, 1 for gandi, 1 for status.io). So i'm opening it either way, we can always fix that later.
irc discussion:
15:25 <+ardumont> fyi, added deposit.s.o in status.io page: https://status.softwareheritage.org/
15:28 <+zack> ardumont: while you're it, it looks like the status.s.o SSL certificate is invalid, filing a task (or fixing it right away, if possible :-)) about that would be nice
15:29 <+zack> i daresay it's a requirement to make that page usable/trustable for visitors
15:29 <+ardumont> that's already referenced in the task opened i think (checking the number)
15:29 <+zack> oh, ok, cool
15:29 <+ardumont> #979
15:29 -- Notice(swhbot): #979 (submitter: olasd, owner: olasd, priority Wishlist, status: Work in Progress): Migrate TLS certificates away from the *.softwareheritage.org wildcards <https://forge.softwareheritage.org/#979>
15:29 <+zack> mmmmh, i don't think it's the same issue
15:29 <+zack> status.s.o has a currently *invalid* certificate
15:29 <+zack> not a wildcard (but valid) one
Migrated from T1916 (view on Phabricator)