raelshark
CDCloudflare Developers
•Created by raelshark on 8/28/2024 in #general-help
Domain proxying not working after updating A record
Yep, the CNAME seemed to solve it.
I recall I'd tested it with CNAME at one point, but WPEngine wouldn't validate the domain and I never saw it propagate. But I also remembered I'd seen that before and tried both with the CF proxy disabled, and it all worked fine. So once it was validated in WPE I went back and turned the proxy back on, and all the traffic started showing up in my CF logs, and was loading the site from WPE. Success!
I also tested a couple of workers routes, and those appear to be working now too.
So it was the CNAME all this time, but with some really complicated underlying circumstances. But a simple solution in the end.
Thanks a lot. This was a big help! I'll also keep note of your other tips at the end, if anything related to this comes up again.
5 replies
CDCloudflare Developers
•Created by raelshark on 8/28/2024 in #general-help
Domain proxying not working after updating A record
@Chaika Super helpful. Been digging into this more - you've definitely pointed me in the right direction. So my understanding is that I DO want the O2O (Orange-to-Orange) enabled for our plan?
According to this it appears to be enabled automatically when using CNAME to
wp.wpenginepowered.com for the Advanced Network we're on, even for non-Enterprise customers.
https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/wpengine/
I think I'll experiment again with using the CNAME to hook things up and see if I can get it working, then I might try reaching out to the PM.
Thanks!5 replies