Custom domain SSL stuck - portal.workcompworld.com not receiving certificate
jdantice
HOBBYOP

2 months ago

Custom domain portal.workcompworld.com has been stuck at "Waiting for DNS update" for over 6 hours despite CNAME being verified as VALID via the API.

Project ID: 73f0da78-129b-4e79-bc7a-cbac0be5b45d

Service ID: 2426984c-05c4-4734-bdb7-c8bfeaf6e76f

Domain ID: 8713da99-d00a-46d6-b73f-9bf46dc75b5e

Domain: portal.workcompworld.com

CNAME target: aywbgixd.up.railway.app

CNAME status (via API): VALID

Port: 8000

DNS resolves correctly - both portal.workcompworld.com and aywbgixd.up.railway.app resolve to 69.46.46.56. HTTP on port 80 works (returns 301 to HTTPS with x-railway-67 header). HTTPS on port 443 serves *.up.railway.app wildcard cert instead of a cert for portal.workcompworld.com.

The domain was deleted and re-added several times today while troubleshooting, which may have triggered a Let's Encrypt rate limit. Please manually trigger SSL certificate provisioning for this domain.

$10 Bounty

1 Replies

Railway
BOT

2 months ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 2 months ago


Your TXT record is malformed. Make sure you're copying the entire content provided by Railway instead of manually selecting the string.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...