a month ago
We have two custom domains on the same service: app.dev.fincom.lu and .app.dev.fincom.lu. Both were working for ~90 days. After what appears to be an automatic Let's Encrypt renewal, app.dev.fincom.lu now shows ERR_CERT_COMMON_NAME_INVALID because it's being served the wildcard cert (.app.dev.fincom.lu) instead of a cert with both domains as SANs. Tenant subdomains (*.app.dev.fincom.lu) still work. We need the apex and wildcard covered by the same cert, or separate certs correctly bound. Same happened to the staging environment.
3 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Have you tried removing the domain from Railway and adding it back after ~10-15 mins? (And updating DNS records if new ones are issued)
0x5b62656e5d
Have you tried removing the domain from Railway and adding it back after ~10-15 mins? (And updating DNS records if new ones are issued)
a month ago
Yes i did. It worked for ~10-15mins and started to prompt same error on the browser again.. Also this is not a proper fix because after three months this probably will happen again
Status changed to Solved wellyngtonquicktools • about 1 month ago
a month ago
For anyone who comes after: SSL are managed on Railway side. Either they issue a proper SAN with the domains or whatever or this will never get a solid solution. In my case i just moved my landing URL inside a subdomain then wildcard certificate works fine.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved wellyngtonquicktools • about 1 month ago