Target shops.myshopify.com. is not allowed for a proxied record.
What is the issue you’re encountering
Cannot create proxied CNAME record for shops.myshopify.com.
What steps have you taken to resolve the issue?
Set up a Shopify dev store with the custom domain dev-store.kelseyjudson.dev. Added a non-proxied CNAME just to get it working (but without O2O). Cloudflare’s documentation for Shopify O2O tells you to create a proxied CNAME, but won’t allow me to do this. I’ve notices many topics on the forums here asking for O2O to be enabled on their account, but I’d like to know why this is necessary? The documentation doesn’t say anything like ‘this won’t work unless you ask about it on the community forum’. So I want to clarify – is this supposed to work normally? Under what circumstances would I need to explicitly ask to have it enabled for my zone/s? This is important to me, as I’m looking into building app features for Shopify merchants around O2O, but that’s only going to work out if there’s not too much friction for my clients enabling O2O for their stores. I also think the documentation could be much more clear about this, as the error you get when you try to create a proxied CNAME to shops.mushopify.com is very confusing considering it’s exactly what the article tells you to do.
What feature, service or problem is this related to?
DNS records
What are the steps to reproduce the issue?
Try to create a proxied CNAME record pointing to shops.myshopify.com.
By the way, the anti-spam measure of no more than 4 links for ‘new users’ makes it nearly impossible to create a topic. There’s no preview, so you can’t see the links that are generated from words like CNAME or Shopify like you can when you’re writing a reply post. I nearly gave up as I just thought it was broken. It’s very frustrating.
It’s now also available to other users, but it currently still needs to be manually activated for every account. I don’t think there’s a timeline as to when this will be “fixed”.
Hmm, so this still applies to everyone (who is not on an Enterprise plan) then? I think the documentation should make that more clear. Currently the only clue from that page is:
But the page implies that it should work for everyone:
You can enable O2O on any Cloudflare zone plan.
While that’s technically true if you reach out on the forums first, it should just say up front that if you’re not on an Enterprise plan then that’s what you’re expected to do.
Obviously I’d much rather it just work for everyone without jumping through hoops, but if there’s no timeline for that then at the very least the documentation could be updated to reflect reality.
Hi @cf-scott , thanks for your reply and for enabling my zone. One of the reasons that I was hoping the documentation might be updated is so I can track the progress of general availability. If the docs won’t be updated, is there any other way I can do this, or be notified when something changes?
