3 hours ago
I am connecting yougetme.club to my running Railway web service and expect it to work over HTTPS. Railway repeatedly reports that TLS certificate issuance failed, so visitors cannot securely open the custom domain, although the Railway-provided domain responds successfully over HTTPS. The issue was still present at the last check on November 19, 2026, at 09:46 PST (17:46 UTC). Please check the domain configuration and certificate provisioning details, identify the failure, and advise on recovery.
Affected resources
- Service: web
- Custom domain: https://yougetme.club
- Railway-provided domain: https://web-production-15b61f07.up.railway.app
- Target port: 3000
- DNS provider: Porkbun
This is a custom-domain certificate failure, not a reported application deployment failure. The user previously reported the web deployment as Active; the currently running deployment ID was not captured. No successful HTTPS connection to the custom domain has been confirmed.
Evidence and attempts
The user reports this exact Railway Public Networking error, recurring after multiple clicks on Try Again:
Failed to issue TLS certificate
An internal error occurred. Please retry or contact supportRead-only checks performed by the assistant on November 19, 2026, at approximately 09:46 PST (17:46 UTC) returned:
yougetme.club A: 153.52.255.75
web-production-15b61f07.up.railway.app A: 153.52.255.75
yougetme.club CAA: no records returned
yougetme.club DS: no records returned
_railway-verify.yougetme.club TXT: a railway-verify record existsThe verification value is omitted from this public draft; it has not been compared against Railway's currently required value.
A curl HTTPS check of the custom domain failed:
curl: (60) SSL: no alternative certificate subject name matches target host name 'yougetme.club'The Railway-provided domain passed TLS verification and returned:
HTTP/2 307
location: /en
server: railway-hikari
date: Thu, 19 Nov 2026 17:46:22 GMTEarlier checks on November 18 found the root domain resolving to Porkbun's parking service, with an HTTP response containing X-Service: pixie-default. The user was instructed to replace the root parking record with a Porkbun ALIAS targeting web-production-15b61f07.up.railway.app. The latest DNS result now matches the Railway-provided domain's IPv4 address, but the current Porkbun record configuration has not been independently inspected.
The target port was previously reported as 2998; a subsequent user screenshot confirmed 3000. The user has clicked Try Again multiple times. Exact retry times and counts, including whether each retry occurred before or after the DNS correction, are unknown.
To reproduce: inspect the custom domain in web → Settings → Public Networking, then open https://yougetme.club or run curl -I https://yougetme.club. Compare with the Railway-provided URL above.
Why contact support?
The Railway error itself suggested contacting support; the user reported that suggestion before the assistant recommended escalation. The assistant recommended support after DNS and HTTPS checks showed the Railway domain responding but the custom domain still failing certificate verification. The specific cause remains unknown, and the assistant has not accessed Railway's certificate issuance or ACME error logs.
Please confirm the required DNS routing target and verification record, inspect the latest validation/issuance error, and advise whether there is a rate limit with a retry-after time, a provisioning failure, or another configuration issue. Repeated retries are a possible factor, not a confirmed cause. Matching IPv4 results do not prove that all DNS records, propagation, or verification requirements are correct.
This is a request for diagnosis and recovery guidance, not authorization to delete or recreate services, domains, databases, or other resources. Please preserve existing Clerk authentication and email DNS records.
Prepared with Railway's support template (v1).
1 Reply
3 hours ago
The domain's ownership verification has passed, and an HTTP request to it now reaches our edge, so the routing is in place for a new certificate attempt. The "internal error" message is a generic fallback rather than a specific diagnosis, and a failed certificate order cannot recover on its own; only a brand-new order can succeed.
Click Try Again on the "Failed to issue TLS certificate" banner in the web service's Settings → Networking now that DNS points at us; that starts a fresh certificate order.
Status changed to Awaiting User Response Railway • about 3 hours ago
Status changed to Solved anna27 • about 3 hours ago