Skip to content
PEDIDO_SUPORTE_RAILWAY_HUMANO_2026-10-18.md.
defynovo-jpg
OP

a month ago

Subject: Certificate stuck for otal.pt and www.otal.pt (service "site") - please re-issue manually

Hello Railway team,

My production site is down for visitors because the certificates for two custom domains are not being issued. Could you please re-issue them manually?

Project: clever-blessing (production environment)

Service: site (port 3000)

Domains: otal.pt (apex, ALIAS to qgys9a46.up.railway.app) and www.otal.pt (CNAME to u6raa3yt.up.railway.app)

Status in the dashboard: "Certificate Authority is validating challenges" / POLLING_AUTHORIZATIONS, for about 1 hour 15 minutes now (I switched DNS at about 01:55 Lisbon time, 18 Oct 2026).

Earlier thread with the automated support (it started a new order but it still has not completed):

https://station.railway.com/support/ssl-certificate-stuck-in-polling-authori-54bfb806

What the automated support found: the first certificate order failed because during validation a DNS resolver still returned the old address 104.18.7.116 (my previous host). I confirmed that this is gone: both authoritative nameservers (ns1.dns-parking.com and ns2.dns-parking.com) now return only 69.46.46.45 for otal.pt, and www.otal.pt is a CNAME to u6raa3yt.up.railway.app. There are no CAA records, no DNSSEC and no AAAA records.

Another domain I added the same way, gestao.otal.pt on another service, got a valid certificate in about 15 minutes, so the setup itself works.

I have NOT deleted or re-added any domain, to avoid the Let's Encrypt duplicate certificate limit.

Could you please:

  1. Check the state of the ACME order for otal.pt and www.otal.pt and re-issue the certificates (or tell me what is blocking them)?
  2. Tell me if I should change anything on the DNS side.

This is a live online shop, so any speed-up is very much appreciated. Thank you!

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • about 1 month ago


a month ago

Your DNS is correct now, so there is nothing to change on that side: both domains point to us and our challenge check reaches your service. The current certificate orders cannot finish because the certificate authority rejected them while it still saw your previous host's address, and a rejected order stays rejected even after DNS is fixed.

We have started a fresh certificate request for both domains, which can take a few minutes to complete.


Status changed to Awaiting User Response brody • about 1 month ago


Railway
BOT

25 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 25 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...