Addtitional info its Route53 and it does not work only for https

Since HTTP works but HTTPS is stuck at “Certificate Authority is validating challenges”, this is almost certainly an ACME validation issue, not an app problem.

With Route53, the most common causes are:

• Using a CNAME at the apex domain (Route53 doesn’t support this). Use an ALIAS record or a subdomain instead.

• A proxy/CDN (like Cloudflare) blocking the ACME challenge path.

• Incorrect _acme-challenge TXT record placement for DNS validation.

• Existing CAA records blocking Let’s Encrypt.

Because traffic already reaches the app over HTTP, I’d start by checking the apex vs subdomain DNS record and whether the ACME challenge can be reached without interference.

Domain: api.conf.realtime.community

CNAME: 72gltupm.up.railway.app (correct)

Issue: SSL stuck on "Certificate Authority is validating challenges"

Debug info:

- No CAA records

- HTTP works, reaches railway-edge

- crt.sh shows no cert ever issued

- curl shows *.up.railway.app cert being served instead

@support
Failed to issue TLS certificate

Try Again

An internal error occurred. Please retry or contact support.

hey this internal error message usually means railway's backend got stuck during cert issuance. i think the fix is to remove the domain from railway service settings, delete the cname record from route53, wait about 10 minutes for dns cache to clear, then add the cname back in route53 and re-add the domain in railway. railway should retry the cert issuance fresh and it typically works within an hour.

doue

Didnt work - moved away from railway