Update:
please i need on my own end, it is extremely urgent,
I am urgently following up on the custom domain issue for piusanyimfellows.org.
The domain was previously stuck on “Awaiting SSL Certificate” for an extended period. After reconnecting the domain, the website started loading for some users, but it is still not stable. Some users can access the site, while others are getting errors such as “Not Secure,” “This site doesn’t support a secure connection,” or the site not loading at all.
Based on the symptoms, this appears to be an SSL certificate/CDN routing issue, possibly involving an incomplete or misconfigured SSL certificate chain, or different CDN/server nodes serving different SSL states. It looks like some users are reaching a server where the SSL certificate works, while others are reaching a route where the certificate is either not fully trusted, not properly attached, or not being served correctly.
Kindly help escalate this to your technical team and confirm the following:
-
Whether the SSL certificate for piusanyimfellows.org has been fully issued and properly attached.
-
Whether the certificate covers both piusanyimfellows.org and www.piusanyimfellows.org.
-
Whether the full SSL certificate chain, including intermediate certificates, is correctly configured.
-
Whether all Figma/CDN edge servers are serving the correct SSL certificate.
-
Whether HTTPS routing is fully active and stable for both the root domain and the www version.
This website is for a live programme portal, and the inconsistent access is affecting users. Please assist in urgently reviewing and resolving the SSL/CDN routing from Figma’s end.
Thank you.
