SSL-certificate for the http-integration url has expired

TTN Network and Services
1

Hi,
the certificate for integrations.thethingsnetwork.org has expired and i wonder if this is the reason i get “400 Bad Request” for downlink requests for http-integration. Im a newby so maybe its unrelated.

Server certificate:
subject: CN=integrations.thethingsnetwork.org
start date: 2018-02-05 12:04:12 GMT
expire date: 2018-05-06 12:04:12 GMT
issuer: C=US; O=Let’s Encrypt; CN=Let’s Encrypt Authority X3
SSL certificate verify result: certificate has expired (10), continuing anyway.

Best regards
Thilo

2

Ouch… can happen, should not.
As www.thingsnetworks.com expires June 7 we will see if the operators are able to automate Let’s Encrypt renewals and also monitor this. For my experience this is one of the less complicated task comparing to operate the whole quite complex LoraWAN backend.

but maybe you should inform support directly?

3

its mentioned in the #OPS channel @ slack so they are aware

5

Looks like there was an instance with outdated config on integrations.thethingsnetwork.org. The current certificate is valid Not Before: Apr 6 12:04:09 2018 GMT Not After : Jul 5 12:04:09 2018 GMT.

I’ll investigate why our monitoring didn’t catch this and why the config wasn’t properly reloaded.