I’m using cloudflare for my domain and also cloudflare SSL cerificate (free).
If I’m accessing my nextcloud server from local LAN via local IP or from outside LAN but using another domain (that is also pointing to my server, with a SSL warning of course - because I’m using cloudflare certificate), the server is answering OK, so it seems all nextcloud configs are OK.
If I’m accessing the server via the designated domain (the one registered in cloudflare), my nextcloud server is answering normally (without SSL warning) BUT extremely slow, and some parts/pictures does not load completely. I need to send several refresh commands until a page is completely loaded.
I’m using port 2053 for secure access (2053 mapped to 443 in my router).
Thanks, but I’m on the free plan, so no Mirage in the free plan, as far as I know
Done. Same result.
I’m lost, I’ve tried every option I could think about.
Looking into dev tools in browser in network, I’ve seen a lot of 522. After every retry, the page is loading “a little bit more” probably combining local cache with cloudflare’s responses. I could say it’s a nextcloud server issue, BUT when accessing the server via any other way from WAN (via direct external IP for example), the pages are loading normally (after initial SSL warning of course, as I’m using cloudflare’s certificate).
There is any way to watch into some logs in cloudflare to understand where is the bottleneck? (Again, I’m on the free plan, I just wanted the SSL and some basic protection from cloudflare)
I really cannot understand where is the problem, as any other way to access my nextcloud server is ok, except via cloudflare registered domain.
I have just a little better results with page rule “cache: bypass”, but still with lost packets. Every refresh/reload gives other missing parts, until a complete page (not always succeed to load full page)
Unfortunately, I use (for the moment) cloudflare SSL certificate, so I cannot test with pause on cloudflare.
As I said in my first message, I’m my own provider.
And again, 522 are partially messages, identified via dev tools in chrome (it’s not a general 522) and these errors does not appear when my nextcloud server is accessed via a different domain pointing to the same external IP or if accessed via the external IP directly (with SSL warning of course).
The pages are completely loaded with normal speed when my nextcloud server is accessed via a different domain pointing to the same external IP or if accessed via the external IP directly.
The problem arise only if accessed via protected by cloudflare domain. Several successive reload/refresh commands usually complete the page.
I’ve attached 2 screen captures, one if accessed via registered and protected by cloudflare domain, the other if accessed via external IP directly. Both captures are made from clean incognito chrome.
It seems that somehow cloudflare certificates are also involved in this issue (beside the - probable - ToS)
I’ve made some tests with another domain, and if using nextcloud with let’s encrypt the speed is normal, but with cloudflare certificates (free) the behavior is exactly as described in the previous posts.