I have a custom domain stuck in a failed certificate state on my service
itsredxo
FREEOP

a month ago

Hi Railway team,

I have a custom domain stuck in a failed certificate state on my service pocketpull-website (project 402de62d-d117-495d-9e79-276a0c2c6033, production environment).

Domain: pocketpulltcg.com

Domain ID: 3e9994c6-03a7-4bf1-bad1-0a53840d6846

Status returned: certificate.status: CERTIFICATE_STATUS_TYPE_ISSUE_FAILED, error message: "An internal error occurred. Please retry or contact support.", marked retryable: true

DNS: the required CNAME (pocketpulltcg.com → 4h9fy4oj.up.railway.app) is confirmed fully propagated and correct — domain ownership shows verified: true.

Could you please retry certificate issuance for this domain on your end? I'd rather not delete/re-add it myself given Let's Encrypt's duplicate-certificate rate limit.

This looks identical to the resolved thread 'Custom domain stuck at CERTIFICATE_STATUS_TYPE_ISSUING for 14 days — DNS correct, retry refused' — same failure pattern, just a different status (ISSUE_FAILED vs ISSUING). Could someone manually trigger a certificate re-issuance the same way sam-a did there?

Thanks,

Red

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 29 days ago


sam-a
EMPLOYEE

a month ago

Your DNS and domain verification for pocketpulltcg.com both check out, and the ACME challenge path reaches our edge correctly, so a certificate re-issuance has been started for this domain. It may take a few minutes to complete.


Status changed to Awaiting User Response sam-a • 29 days ago


itsredxo
FREEOP

a month ago

thanks, confirmed working


Status changed to Awaiting Railway Response Railway • 29 days ago


Status changed to Solved itsredxo • 29 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...