a month ago
The edge proxy refuses to route claw.capcofire.com despite the database showing syncStatus: ACTIVE and the domain being correctly registered. The SSL certificate also never gets provisioned (always empty), even with correct DNS.
The domain is back on clawdbot with a new CNAME: lgxvionz.up.railway.app. Please update your DNS one more time, then open a Railway support ticket referencing:
- Domain:
claw.capcofire.com - Project: CAPCO Design Group (
7defe707-81a1-48a5-8844-c2672ddcf294) - Service: clawdbot-railway-template (
869bc903-1cae-4623-8cfd-8f55c30629a2) - Edge ID:
edge-500b32d4e9aaa4d3ff91d6ebb54285cd - Issue: Domain shows
syncStatus: ACTIVEbut edge returns 404 withx-railway-fallback: true. SSL cert never provisioned. Previously attached to deleted project CAPCLAW (1fdb60f0-77e0-4880-a15d-5c9f5d707ab8). No stale DB entries found. Same edge as working domainap.capcofire.com. Domain fails on multiple services.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your CNAME for claw.capcofire.com currently points to uxq9qp3u.up.railway.app but needs to point to lgxvionz.up.railway.app. Additionally, the TXT record at _railway-verify.claw.capcofire.com contains a stale token from the previously deleted project and needs to be updated to railway-verify=863edb33d33fc6ce897c5d3214e0297f8be3b0f66cce915182f08c19fc31924d. The 404 fallback response and missing certificate are expected until both records are corrected. Your working domain ap.capcofire.com has the correct CNAME and a valid verification token, which is why it routes and has a valid certificate.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago