This adds an accordion that will present any ingress that have stale acme challenges. The accordion will only display if any are detected.
I've linked to the going-live documentation, but this could probably be better placed in its own section along with build errors and warnings maybe?
>> Lagoon detected routes that have stale acme certificate challenges.
This indicates that the routes have not generated the certificate for some reason.
You may need to verify that the DNS or configuration is correct for the hosting provider.
https://docs.lagoon.sh/using-lagoon-the-basics/going-live/#routes-ssl
Depending on your going live instructions from your hosting provider, you may need to make adjustments to your .lagoon.yml file
Otherwise, If you no longer need these routes, you should remove them from your .lagoon.yml file.
> The route 'test.example.com' has stalled certificate challenge
reason: order is in "errored" state: Failed to create Order: 400 urn:ietf:params:acme:error:rejectedIdentifier: Error creating new order :: Cannot issue for "test.example.com": The ACME server refuses to issue a certificate for this domain name, because it is forbidden by policy
> The route 'fail.example.com' has stalled certificate challenge
reason: order is in "errored" state: Failed to create Order: 400 urn:ietf:params:acme:error:rejectedIdentifier: Error creating new order :: Cannot issue for "fail.example.com": The ACME server refuses to issue a certificate for this domain name, because it is forbidden by policy
This adds an accordion that will present any ingress that have stale acme challenges. The accordion will only display if any are detected.
I've linked to the going-live documentation, but this could probably be better placed in its own section along with build errors and warnings maybe?