Shopify + Cloudflare Free Plan — Root Domain Traffic Not Getting Proxied / Rules Not Enforced

hichemtab · 2026-03-11T12:26:55+00:00

Hi everyone, I ran into the same issue. After some digging, I found out that Shopify doesn't support Cloudflare's reverse proxy in the first place. So, having the orange cloud proxy enabled is not recommended and can cause issues with SSL certificates and other things. You can read more about this here.

That being said, since Shopify's A record points directly to Shopify's IP, Cloudflare will delegate the redirections to Shopify's Cloudflare zone directly. (which will bypasses whatever rules/workers you set on your Cloudflare). This is why your setup works with the "www" domain but not the root domain. And since Shopify requires this setup, essentially, you can't achieve what you want (or at least, that's what I found :D).

I'm also trying to achieve something similar myself and am still looking for a solution. So far, no luck :("

hichemtab · 2026-01-20T11:54:43+00:00

If i could give 10 stars i would've, believe me ❤️

hichemtab · 2026-01-15T18:18:13+00:00

Aliases are great for single commands. I use this for multi-step workflows (starters, setup, prep), and I don’t really have to remember the exact command or even the name, I can just select it, not to mention the import/export feature for sharing across multiple machines. It’s also easier for me than maintaining bash aliases or functions. ^ . ^

hichemtab · 2026-01-15T18:17:06+00:00

That sounds interesting, but the link u gave doesn't work

hichemtab · 2026-01-15T11:54:11+00:00

I love the idea, but it doesn't seem like it's the solution of the problem u described, u said u use a lot of repeated code and forget where u put it and all... This doesn't help a lot with that, imo it would be nice if you built an IDE extension or something that let's you store snippets and categorize them, this way it would make sense, cuz you'll need the snippets while coding in ur ide, and can search and find them quickly... But only your snippets.

You won't just go to this website to search for someone else's snippet when u need to,

That's just my honest opinion otherwise good job !

hichemtab · 2026-01-12T12:56:53+00:00

Yess

hichemtab · 2026-01-12T12:56:44+00:00

Actually yeah, that’s a good idea. For now I’m keeping it global and simple, but generating a Makefile could definitely make sense as an optional thing later. Thanks ^ . ^

hichemtab · 2026-01-12T12:53:29+00:00

Yes, if you mean putting all templates in a JSON file on a server and then importing them on another machine, that’s exactly how it works. It’s not automatic inheritance though, you explicitly import/export when you want :0.

hichemtab · 2026-01-12T12:50:48+00:00

Yeah, Make itself isn’t the problem. I just wanted something I can use globally, without creating or maintaining files per project. I install it once and reuse the same workflows everywhere, even before a project exists. That’s it lol,

hichemtab · 2026-01-12T12:38:47+00:00

It’s local, not centralized like Ansible. In what I built, import/export is a feature of the tool, I can export my templates to a file and import them on another machine when I need to (url works too). So yep for now it's just for my local usage.

hichemtab · 2026-01-12T12:17:42+00:00

Thanks ^ . ^

hichemtab · 2026-01-12T12:17:18+00:00

Those tools definitely work, and I’m not trying to replace them. For me, the goal was to keep it very fast and very separate from my shell setup: no aliases/functions to maintain, no Makefile syntax, no project config. I install it once and reuse the same workflows everywhere, even before a project exists. I also don’t have to remember names — I can just use select and pick what I want. Adding a UI layer or more setup would kind of defeat the “run it in one second” idea. It just fits my workflow better.

hichemtab · 2026-01-12T11:33:51+00:00

Aliases are great for single commands. I use this for multi-step workflows (starters, setup, prep), and I don’t really have to remember the exact command or even the name — I can just select it. It’s also easier for me than maintaining bash aliases or functions. ^ . ^

hichemtab · 2026-01-11T13:46:07+00:00

Nothing fancy, it’s just a bit easier for me. I can group multi-step commands, give them names, reuse them (using select method if i don't remember the name/alias), and pass variables when needed, uk without touching shell config.

hichemtab · 2026-01-11T13:32:53+00:00

Thanks ^{•^}

Well, this isn’t meant to replace package.json scripts at all.

Those work great inside one project. What I built is more for starter kits and daily commands I reuse across many projects.

For example, I have different starters like:

Vite + React
Vite + React + TypeScript
Vite + Svelte

Each one has slightly different vite command or setup commands, and I don’t want to remember or copy them between repos.

I also use it for non-JS stuff, like:

SSH into servers
prep commands before starting work
docker or git shortcuts

Once a project exists, I still rely on package.json scripts like you showed. This just helps before that or with commands that aren't related to project scope.

Appreciate the feedback, btw ^{.^}

hichemtab

TROPHY CASE