Dan Di Gregorio

Ok, I still have to understand completely the plugin functionality with QC but I close this thread as Resolved. Thanks a lot for your patience and assistance.

Dan

Ok, so just to understand better: when the page will be served by the closest QC pop to the guest visitors? This is important to reduce the TTFB.

So, it could be normal that x-qc-cache returns “miss” in a guest first visit?

• Drop domain setting set to ON
• Sitemap refreshed
• Pages recrawled

But the problem still persists: https://prnt.sc/uwIARpmNMqL-

Report number: QAJAGGVQ

Ok, my hosting provider fixed the webserver issue and now it appears as Litespeed, I’ve regenerated all the sitemap and launched the crawler for all pages, but….the problem seems to persist: https://prnt.sc/cKmSFhKMCef9

Report number: KZJTAETW

The hosting support fixed this issue. Now the webserver is detected as “Litespeed” instead “Apache”. Both webserver was trying to run in the same time causing a conflict.

Now I’ll make some test to provide a feedback soon in order to mark this request as “Fixed”, I hope….

Dan

Ok, it’s clear. Finally I think we’ve catch the problem. I’ll open a ticket with the hosting support and I’ll get back asap with news.
Thanks a lot

Here the webserver setting in my sPanel: https://prnt.sc/tzJz0IX9NFI6

Anyway, I’ll restore the Scalahosting DNS to verify the headers responses and I’ll update this thread.

• This reply was modified 9 months, 3 weeks ago by Dan Di Gregorio.

But I am on a litespeed webserver. My website is hosted by Scalahosting with Litespeed Server Enterprise.

You can verify in headers response > https://prnt.sc/xVrVpenprfX9

I am using the QUIC cloud DNS in order to avoid the CNAME setting in NS records, but I am on a Litespeed server for sure. Could the QUIC DNS cause this problem??

• This reply was modified 9 months, 3 weeks ago by Dan Di Gregorio.

Hello, thanks for your answer.

I’ve changed the Drop Domain setting, reloaded the sitemap, re-launched the crawler but the problem still persists.

Here the screenshot: https://prnt.sc/EYHR595sGiyr

Ok, thanks for support.

Report number: BOKKFFDE

Report date: 02/06/2024 09:50:54

Hello, now the sitemap appears normaly. I don’t know the reason why it was not working before. The only change I made is enabling the crawl at server level. May be this was the problem?

Dan

Hello, I’ve already tried several time to save https://dicasdomundo.com.br/sitemap_index.xml under “Custom Sitemap” but the response is the same: “No valid sitemap”. I’ve just tried to put page-sitemap.xml after to verify if something changed, but nothing changes.

Just another info: I’ve set the Quic.cloud NS for the domain name. I don’t know if this may affect the plugin behaviour.

• This reply was modified 9 months, 3 weeks ago by Dan Di Gregorio.
• This reply was modified 9 months, 3 weeks ago by Dan Di Gregorio.