Our custom domain hbcclub.com.tw has been stuck for more than 72 hours.

Railway resource IDs:

• Project: valiant-tranquility (d341f752-6537-41c9-a41d-51a973398cf6)
• Environment: production (efd6c094-cd68-4f32-a7a6-e50ab012d188)
• Service: haoding-commerce-platform (10c09082-3742-4cba-9b21-ccbf1f372867)
• Domain: f60b5620-f197-41d4-815e-1ce5b4747be9
• Deployment: 0a61f6c6-9b11-49a6-9b5b-da20cc32eb65
• Target port: 8080

Latest state (2026-09-02 09:37 Asia/Taipei):

• Cloudflare NS and apex A/AAAA resolve normally.
• The ownership TXT is public and exactly matches Railway's current required value.
• No CAA restriction or conflicting apex A/CNAME was found.
• Railway domain sync is ACTIVE and traffic DNS is PROPAGATED.
• Ownership remains verified=false.
• Certificate remains ISSUING.
• HTTPS returns 404 with x-railway-fallback=true.
• Railway request ID: 4jOkj4OmTgSC-oFVn6XIxQ
• The Railway-generated service domain is healthy: live=200, ready=200.

We invoked the official certificate retry command once on 2026-08-31, but Railway rejected it before mutation because the certificate is still ISSUING rather than FAILED. We did not retry again, delete/recreate the domain, or modify DNS.

Please inspect the control-plane ownership reconciliation, certificate issuance job, and edge route binding for this domain. If safe, please manually re-trigger ownership verification, certificate issuance, and route binding without deleting the domain. The raw ownership token is intentionally omitted; Railway can compare it internally.