12 days ago
CNAME on the * record is very old and not updating after long periods of time. Its seems stuck? But the acme record is updating quickly and finding the DNS.
5 Replies
12 days ago
Hey, could you explain a little bit more about what's happening? Are you trying to add a wildcard domain and it's taking a while to set up? Screenshots are welcome too
I think it might have been my lower environemnt screwing it up somehow.
I have a test.[nav.education](nav.education) CNAME in a "lower" test env
and I have a *.nav.education in my higher environment that wouldn't resolve.
I think this is causing issues with some cookie retention because of missmatched SSL's in my production app.
I removed my CNAME record in cloudflare for test.[nav.education](nav.education) and I think its resolved now?
I'm not sure whats going on under the hood to look up that CNAME on railway's side but I"m not sure its accounting for that type of situation 😂
tl;dr
prod had a CNAME for custom domain at *.nav.education
test env had a CNAME for test.nav.education
prod was having issues giving me green checks and said it wasn't setup right in cloudflare….
11 days ago
Maybe it just needed a little more time to finish the setup. I'm glad it's working now. Do you have any more issues?