NitroCache - Cloudflare

Hello!

I use Opencart v3020 with Journal theme and php v7.3.
Our site is running from Cloudlare and have changed nameservers to Cloudflare.
All is running smooth and we have no error in Opencart error log.

The problem comes when installing the Nitro Cache.
After installation you get no error and nothing in error log.
You can see that pages loading faster and so on.
You can add a product to cart.
BUT when you go to checkout/checkout
You get "502 Bad Gateway" and under that you see "cloudflare"
I contacted the host and they say it is Nitro Cache creating the error but the Nitro Cache works if I disable the Cloudflare and load from host.

Have anyone seen or had this issue before?
I have tested almost everything so my brain is not in function anymore
If anyone knows how to fix it?
I can pay you if it helps....

Cloudflare is nothing more than a distributed cache (and fairly useless unless you sell digital downloadable products), nitro is nothing more than a server cache, Journal is a template which caches virtually everything it can lay it's hands on (it has to as it is rather slow on it's own).

So now you have cached assets of cached assets of cached assets and you wonder why things start to behave strangly.

Quick solution: disable Cloudflare, uninstall Nitro, use Journal cache and be happy.

letxobnav wrote: ↑

Mon Sep 23, 2019 6:52 pm

Cloudflare is nothing more than a distributed cache (and fairly useless unless you sell digital downloadable products), nitro is nothing more than a server cache, Journal is a template which caches virtually everything it can lay it's hands on (it has to as it is rather slow on it's own).

So now you have cached assets of cached assets of cached assets and you wonder why things start to behave strangly.

I do understand what you mean.
We use Journal as theme but I do not use their cache system at all.
Right now I only have Cloudflare´s in-built system with Minify options enabled.
Checked speed many times and I have E for speed and loading time 2,5sec.
Without Cloudflare we had E for speed and loading time 5,5-6,0 sec.

So my thought was to install Nitro and only use Nitro for page cache, nothing else.
When we had Nitro enabled before move to this new host we had B for speed and loading time 3,5 sec.
But maybe you any other page speed extension I can try instead? I´m open for everything

thekrotek wrote: ↑

Mon Sep 23, 2019 8:43 pm

Quick solution: disable Cloudflare, uninstall Nitro, use Journal cache and be happy.

Journal itself I think is way to slow. It can work as theme but nothing else.
I have not really checked so many themes but to change theme can help too.
I think the front page is most important of all, if a site has a very slow first page it´s most likely that I will find another one for buying. Just how I do
Do you use Journal?

Druvan wrote: ↑

Tue Sep 24, 2019 3:22 am

Journal itself I think is way to slow. It can work as theme but nothing else.

Exactly. This is why it caches all the stuff.

Druvan wrote: ↑

Tue Sep 24, 2019 3:22 am

I have not really checked so many themes but to change theme can help too.

And you actually should. It is highly recommended to get rid of the Journal.

thekrotek wrote: ↑

Tue Sep 24, 2019 3:32 am

Druvan wrote: ↑

Tue Sep 24, 2019 3:22 am

Journal itself I think is way to slow. It can work as theme but nothing else.

Exactly. This is why it caches all the stuff.

Druvan wrote: ↑

Tue Sep 24, 2019 3:22 am

I have not really checked so many themes but to change theme can help too.

And you actually should. It is highly recommended to get rid of the Journal.

Do you have any theme in mind?
I´m open to test something.

The problem with those "speed scores" is that they only measure "first page" speeds.
That is one reason why journal puts everything inline (the other has to be layziness) as it is great for "first page" speed scores as it decreases requests for assets.

The problem is, non of that inline stuff is cached in the browser so any subsequent page request has no benefit of browser caching and all drawbacks of bloated html sources. I.e. fast first page, slow average page.

The same with cloudflare, they cannot cache what the browser cannot cache and as such the speed increase only works on "first page" loads (distributed assets), any subsequent page is not faster as the browser caches the same. Any non-cacheable content is always slower as you add an additional network hop because cloudflare has to get that stuff from your host always. So those CDN's are only worth it if you sell downloadable products as those can be cached distributed by them and as such greatly increase download speeds and decreasing your host loads. But for normal e-commerce they add little value.

So you have to determine if fast first page loads is more important than fast average page loads to you.