Pain point · Self-hosting & upgrades · Blocks work
Inconsistent Redis TLS verification across API and clock
2 source threads · first seen 2025-10 · last seen 2025-12
Summary
The API connects to TLS Redis without verifying the certificate while the clock process requires verification, so one component fails to connect.
- Affects
- self-hosting team using TLS Redis
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“making it impossible to connect to a server using self-signed certificates”
“In our (testing) deployment, it makes it so that the API works properly, but the clock fails to connect to Redis”