When REDIS unavailable, there is a risk of LetsEncrypt quotas exhaustion

When working with REDIS adapter for storing certificates:
If REDIS is unavailable, sequence of attempts to connect with HTTPS may cause a sequence of requests to LetsEncrypt to be set and an exhaustion of quota (causing a 1 hour freeze).

We should introduce a logic that will protect from the above scenario.

Start by tracing the Redis adapter failure path and the sequence of HTTPS requests made to Let's Encrypt. Define and implement protection against repeated certificate requests when Redis is unavailable, then verify that the failure path no longer risks quota exhaustion or the reported one-hour freeze.

Written by the indexing model from the issue text.