ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Pending custom-domain certificate on Scalingo A custom domain on Scalingo shows a pending managed certificate status after DNS records were added and pointed to the platform. The goal is to determine whether the delay comes from DNS propagation, a Let's Encrypt rate limit, or a stalled platform-side provisioning retry. Certificate lifecycle is tied to the ap
A development workflow uses ngrok HTTP tunnels to expose a local service at a stable public URL for webhook and callback testing. The goal is to keep one reserved domain bound to the same local endpoint across restarts, with TLS handled entirely by ngrok's automatic certificate provisioning. The open point is how ngrok's domain naming transition affects that
Goal To understand the current limitations and future plans for serving multiple subdomains under a single custom domain on Read the Docs using HTTPS. Constraints Read the Docs automatically issues a free Let's Encrypt certificate for each custom domain that points to readthedocs.org via a CNAME (or an A/ALIAS record for apex domains). The platform does not
CodePen Projects allow Pro users to map custom domains via CNAME records to host front-end demonstrations. While the platform supports this integration, the specific lifecycle of the SSL/TLS certificate provisioning process remains underspecified in the technical documentation. When transitioning a Project from a CodePen URL to a custom domain, there is unce
Read the Docs allows projects to be mapped to custom domains, utilizing Let's Encrypt for SSL/TLS certificate management. This process typically requires a CNAME record to point the domain to the Read the Docs infrastructure to facilitate domain validation and certificate issuance. When utilizing external DNS providers with strict propagation policies or spe
scalingo
ngrok
readthedocs