Closed adamkoppede closed 1 week ago
Visit the deploys page to approve it
Name | Link |
---|---|
Latest commit | 05e92c8ed5f75a961af58ade89c87a8d6c048cb3 |
I don't think my issue was related to #203, because there the route is eventually successful after some failed attempts. This wasn't the case for my TLS certificate mis-configuration. But this change may help anyways, if lighthouse sets the runtime error field there.
Good idea, thanks! Will get a release out a bit later today most likely.
For me, an absent NODE_EXTRA_CA_CERTS environment variable caused the lighthouse tasks to fail due to invalid TLS certificates after an upgrade in a containerized environment. In that case, the existing error message wasn't helpful, because the same URL worked fine on the host where the certificate was correctly installed and picked up.