ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
CERTIFICATE_VERIFY_FAILED when mapping Cloud Run custom domain via CNAME Goal: Verify that a custom domain mapped to a Cloud Run service can be accessed over HTTPS without TLS hostname mismatch errors. The current setup uses a CNAME record pointing the subdomain to the Cloud Run service URL. Clients report CERTIFICATE_VERIFY_FAILED during TLS handshake. Cons
Integration boundary I am terminating HTTPS on a global external Application Load Balancer using a Google-managed SSL certificate, with the domain's DNS hosted in Cloud DNS. The goal is to understand the validation lifecycle between these two components before relying on managed certificates for production cutovers. Observed behavior and uncertainty Document
I am planning a zero-downtime migration of a small web application from an on-premises origin to Google Cloud (Cloud Run behind a Global External HTTP(S) Load Balancer). The intended design keeps the legacy origin serving traffic while the GCP backend is health-checked, then shifts traffic gradually rather than flipping a single record. Two supported mechani
