Skip to content
TLS certificate for branchoutdoors.app stuck at ISSUING / POLLING_AUTHORIZATIONS after rate-limit failures
sarahrittertech-commits
OP

25 days ago

I'm trying to serve my service on the custom domain branchoutdoors.app, which I bought through Railway. The domain shows as verified, but its TLS certificate is never issued. The first attempt failed with a Let's Encrypt rate limit. Since I removed and re-added the domain, it has stayed at ISSUING / POLLING_AUTHORIZATIONS for hours, across two re-adds. Because .app requires HTTPS, the site doesn't load on the domain at all. It's still happening. Could you check the certificate (ACME) order for this domain on your side and get a certificate issued, or tell me what I need to change?

Resources

Workspace: sarahrittertech-commits's Projects

Project: branch-outdoors (ID bece2de8-d0af-427b-b16e-3db65bc0af45), environment production

Service: outdoorscommunityapp (ID 6e61ac9f-3b04-43b3-bca4-cddb56c9e8f6), target port 8080. The service runs normally at https://branchoutapp-production.up.railway.app.

Custom domain: branchoutdoors.app, current domain ID 3a31c6b0-4622-48fc-b503-c1674ff5eecf, CNAME target shown by Railway: ctcgomq4.up.railway.app

Earlier IDs for the same domain, both removed: 566bee2b-736d-4d29-bbc8-54963f79d2b2 and 2092288f-fb10-49fc-a157-c672a638395b

The domain was bought through Railway's domain purchase, so DNS is on Railway-managed name.com nameservers (ns1kpv, ns2cvx, ns3gnv, ns4fpy.name.com). I have not edited DNS by hand.

Timeline (26 October 2026, UTC, from railway domain status)

18:11, last known success. Added branchoutside.app (another domain bought through Railway) to the same service. Its certificate was VALID within minutes and HTTPS worked. That domain has since been removed.

18:11. Added www.branchoutside.app. Its certificate went to ISSUE_FAILED.

18:56. Added branchoutdoors.app (ID 566bee2b-…). Verified, then ISSUE_FAILED with the error below. A retry was refused.

About 20:55. Removed it and re-added it (ID 2092288f-…). Status: ISSUING, detail POLLING_AUTHORIZATIONS. Still the same at 21:35 and 23:45.

About 23:46. Removed and re-added again (ID 3a31c6b0-…). Status went from FETCHING_AUTHORIZATIONS to POLLING_AUTHORIZATIONS and stayed there through about 6 minutes of watching. This is the last observed state.

Error from the first branchoutdoors.app attempt and from www.branchoutside.app:

Certificate status: CERTIFICATE_STATUS_TYPE_ISSUE_FAILED

Certificate error: Let's Encrypt rate limit reached. Please wait before retrying.

Certificate error type: CERTIFICATE_ERROR_TYPE_RATE_LIMIT

Certificate retryable: false

railway domain certificate retry returned: Certificate retry is not available for this failure. Let's Encrypt rate limit reached. Please wait before retrying.

Around 18:00 UTC the Railway dashboard showed this banner: "TLS certificate issuance returning rate limit error. We've found the cause and are working on a fix."

Checks, run from my machine after the last re-add

branchoutdoors.app A record (from 8.8.8.8 and from ns1kpv.name.com): 69.46.46.126. ctcgomq4.up.railway.app also resolves to 69.46.46.126, and whois lists that address as Railway's (NetName RLWY-HIKARI-01, OrgName Railway). No AAAA record and no CAA record on the domain or on app..

http://branchoutdoors.app/.well-known/acme-challenge/test returns 404, served by Railway's edge.

https://branchoutdoors.app/ fails with curl: (60) SSL: no alternative certificate subject name matches target host name 'branchoutdoors.app'.

The _railway-verify TXT record still shows the token from the first add (railway-verify=80460501…). Railway reports the domain as Verified: yes anyway.

CLI: Railway CLI 5.71.0. Version 4.37.2 returned "Unauthorized" when adding a domain, even though railway whoami worked; upgrading fixed that.

Why contact support

The AI assistant I was working with (Claude Code) suggested it. Two remove-and-re-add attempts didn't help. DNS appears to point at Railway, and the state of the ACME order is only visible on Railway's side.

Not tried

Another suggestion was to delete the apex A record and add an ALIAS to ctcgomq4.up.railway.app. I haven't done that, because the A record already resolves to the same address as that target. If DNS does need changing, please say exactly what to change.

Hypothesis (unconfirmed)

The order may be stuck from the earlier rate limit, or an authorization from a removed attempt may still be pending. This isn't confirmed.

Constraints

The site is in a soft launch (not public yet), so brief downtime on the domain is fine. I'd rather not delete DNS records I didn't create unless you confirm it's needed.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 25 days ago


dizzydes90
EMPLOYEE

25 days ago

Your DNS is fine, nothing to change there. branchoutdoors.app resolves to our edge and the domain is verified on our side, so leave the A record and the verification record as they are.

The domain entry is no longer stuck at POLLING_AUTHORIZATIONS. Its last attempt ended in a failed state on our side, and unlike the earlier rate-limit failures this one can be retried. Open the service's Settings, then Networking, and click Try again on the failed certificate banner for branchoutdoors.app. The certificate should go valid within a few minutes.

The rate-limit failures you hit on Oct 26 came from an account issue with our certificate provider that is now fixed, not from your domain or DNS. Sorry for the time this cost you. If Try again does not produce a valid certificate, say so here and we'll re-issue it from our side.


Status changed to Awaiting User Response Railway • 25 days ago


dizzydes90
EMPLOYEE

25 days ago

Following up on this morning's message: a new certificate has now been issued for your custom domain, so there is no need to click Try Again or to remove and re-add it. The domain was left exactly as it was, with the same DNS target and verification record, and HTTPS is serving on the hostname. If a browser still shows the old warning, that is a cached result and a fresh connection clears it.

Your DNS was correct throughout; the failure was not caused by anything on your domain.


Status changed to Solved dizzydes90 • 25 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...