Forum Discussion
Hi ysantos
Sorry to hear about the problem you're facing.
Not so certain for whats going wrong here. Have you tried restarting the Scim bridge? Confirm the external IP you have configured against changes. If it changes you'll need to change your DNS record to point to the new IP. Could be possible for DNS record created before your SCIM bridge was created/online - which didn't allow the DNS change enough time to propagate.
If everything is fine, then indication of the problem is that the AAA record for Let's Encrypt might be missing so that it can assign a TLS certificate. Can you confirm if a CAA record exists with your domain's DNS records that would allow Let’s Encrypt to issue certificates for your dns sub-domain?
The Let's Encrypt documentation on Certificate Authority Authorization (CAA) provides instructions and examples on how to create this record if it doesn't already exist.