3 months ago
- Cert: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP — unchanged for ~36 hours
- CNAME target: curl -sk https://v3l6449i.up.railway.app/health → {"status":"error","code":404,"message":"Application not found"}
- Service domain: curl -sk https://codex-gateway-production-835e.up.railway.app/health → {"status":"ok"} (works fine)
- SSL cert served: CN=*.up.railway.app (wildcard — custom cert never issued)
- DNS: CNAME propagated, currentValue matches requiredValue per your API
- Cloudflareproxy: OFF (grey cloud / DNS-only)
- syncStatus: ACTIVE, edgeId: edge-6705e5cc5ae5e82ae931d2b1f900f08f
The core problem seems to be that the edge binding (v3l6449i.up.railway.app) isn't routing to the deployment. The service domain works, the custom domain's CNAME target doesn't.
Could you check if the edge is correctly bound to the service instance?
Project: codex-gateway
ServiceID: 287e54ee-63b5-420e-a7dc-1330ee5bbfdd
CustomdomainID: a68b8469-64fc-4cef-b952-42edad990f97
2 Replies
3 months 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 • 3 months ago
3 months ago
👆 I second this. My deployment pre-dates (9 months old) this new 3rd TXT record requirement for custom domains. I was experiencing SSL 525 errors, went through all documented debugging steps and nada. Then I just "recreated" my custom domain and voila.
If you don't see 3 domain records required to configure your custom domain (particularly this new TXT record), then delete and add your custom domain again and you should.