SCIM Bridge SSL Error

Hi @PaulBeaudry. Thanks for reaching out. My name is De Ville and I am part of the provisioning team.

Thank you for providing the log output. From the logs I can see that you are running the latest available version of the SCIM bridge (2.3.1). This is great since we included some fixes related to the certificate issuing via Let's Encrypt.

I wanted to confirm a few things, which will help me provide better guidance:
1. Can you confirm that your DNS record is configured correctly for your domain? I.e. that the domain is pointing to the IP address of the host where your SCIM bridge is deployed.
2. Can you confirm that the SCIM bridge is publicly accessible on the internet? Let's Encrypt will reach out to the SCIM bridge with a challenge before issuing a new certificate for the domain.
3. Do you have any additional environment variables or config options set? From the logs I can see that Let's Encrypt is running in test mode and is using the staging servers (acme-staging-v02) instead of the production servers (acme-v02). The environment variable that controls this behavior is called OP_LETSENCRYPT_TEST_MODE.

In most cases the SCIM bridge should be able to obtain a certificate from Let's Encrypt when the DNS record is correct and the SCIM bridge can be accessed publicly.