Stream: registry.fhir.org
Topic: build.fhir.org certificate has expired
Tyge Folke Nielsen (Jan 04 2022 at 14:03):
The SSL certificate for fhir.org (including build.fhir.org) seems to have expired two days ago. I have had strange errors from sushi and download:
wget -O dk-core.package.tgz https://build.fhir.org/ig/hl7dk/dk-core/package.tgz
--2022-01-04 14:25:29-- https://build.fhir.org/ig/hl7dk/dk-core/package.tgz
Resolving build.fhir.org (build.fhir.org)... 35.190.153.146
Connecting to build.fhir.org (build.fhir.org)|35.190.153.146|:443... connected.
ERROR: cannot verify build.fhir.org's certificate, issued by ‘CN=Go Daddy Secure Certificate Authority - G2,OU=http://certs.godaddy.com/repository/,O=GoDaddy.com\\, Inc.,L=Scottsdale,ST=Arizona,C=US’:
Issued certificate has expired.
An SSL server test reveals: Valid until Sun, 02 Jan 2022 11:47:06 UTC (expired 2 days, 1 hour ago) EXPIRED
Where can I report this issue ?
Kevin Power (Jan 04 2022 at 14:28):
This has been reported on a couple of streams (#shorthand and #IG creation ) and it seems it needs to be addressed by @Grahame Grieve ?
Wayne Kubick (Jan 04 2022 at 18:24):
Apologies, all. I was under the impression that Grahame had assigned a backup for this some time ago. But I believe he'll be able to take care of this in a day or 2.
Jens Villadsen (Jan 04 2022 at 18:25):
The community found a way out at https://chat.fhir.org/#narrow/stream/215610-shorthand/topic/R5.20support/near/266698054
Jens Villadsen (Jan 04 2022 at 18:26):
But it is not a sutainable solution that there is only one person with the keys @Wayne Kubick
Wayne Kubick (Jan 04 2022 at 18:27):
Thanks, Jens. Again, this will be addressed in a sustainable manner shortly.
Jens Villadsen (Jan 04 2022 at 18:28):
I hope so ... The community (only) thrives best when it is supported by a solid tool chain and solid infrastructure
Last updated: Apr 12 2022 at 19:14 UTC
