24 days ago
Hello Railway Community,
I need assistance with a TLS certificate issuance problem affecting our production backend.
Domain: api.stemlantern.com
Service: stem-backend
Environment: production
Plan: Hobby
I recently added api.stemlantern.com as a custom domain to this Railway service for the first time.
Railway confirms that the domain is verified and DNS has propagated, but its Public Networking settings display:
Failed to issue TLS certificate
"Let's Encrypt rate limit reached. Please wait before retrying."
The certificate status is ISSUE_FAILED, and automatic retry is unavailable.
When I visit https://api.stemlantern.com/api/health in Google Chrome, I receive:
- Your connection is not private
NET::ERR_CERT_COMMON_NAME_INVALID
The backend deployment itself is successful, and the service is online. The issue appears to involve certificate provisioning rather than application deployment.
Could someone from Railway please clarify:
- Why would the Let's Encrypt rate limit be reached during the initial certificate issuance for this domain?
- Is there a known certificate-provisioning or DNS configuration issue that could cause this?
- What is the recommended way to recover certificate issuance, and when would another attempt be safe?
- Can Railway help resolve this without requiring me to remove and re-add the custom domain?
I haven't deleted or recreated the domain because I don't want to cause additional rate-limit problems.
I've attached screenshots of the Railway error and Chrome's certificate warning.
Thank you for your assistance.
1 Reply
24 days ago
The certificate for your domain has now been issued and shows as valid, and HTTPS requests to it are reaching your stem-backend service, so there is nothing to remove, re-add, or retry. If Chrome still shows the warning, close the tab and reload, since the browser can hold onto the earlier failed connection.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved somtico • 24 days ago