Our infra team reverted the Cloudflare proxy changes, revoked the certificates and redeployed the platform components.

The client decided to move back to their hosting provider's ISP and DNS service after the situation normalized across the country. This resulted in the platform's instability due to conflicting SSL certificates.

The DNS and Proxy have been moved to Cloudflare and platform services received valid SSL certificates.

In order to resolve the underlying issue of connectivity, the infra team suggested moving the DNS and Proxy services to Cloudflare (after performing feasibility analysis and tests)

Further investigation of infra team revealed the issue was actually related to the ISP (Kazakhtelecom) and several ISPs and their clients have been affected all around the country:

https://community.letsencrypt.org/t/lets-encrypt-is-not-available-from-kazakhstan/235938/17?u=01edu

The issue persisted for more than 48 hours and a member of the hosting provider was granted access to the server upon client's request despite the fact the infrastructure team's diagnosis of the issue being on the ISP side.

The issue remains unresolved by the ISP/Hosting provider, and the client insisted on resolving the problem locally by alternative methods. This unorthodox approach didn't resolve the underlying issue.

Our platform is up and running since the last deployment and the server itself is online. This issue related to SSL stems from the Hosting Provider's ISP.