Is UCSS and CCSS working?

Can you please check another log for the problem with UCSS and CCSS does not seem to upload to Quic Cloud, even though I click on the “Run queue manually” button?

https://pastebin.ubuntu.com/p/cKqbdcgWXN/

I deleted my domain in QC and then re-installed/re-connected it to my website, and now it seems the problem is back, so even though the UCSS and CCSS files seems to be sent from Litespeed cache plugin, they do not appear in QC.

Thank you very much for your help!

[90.235.92.148:12346 1 mXb] ??? ? Response code is not 200 in self_curl() [code] 404

server IP set correctly ?

Hello and thank you for your response.

Yes, this time it should be right. The first time you helped me it was incorrect, but I have now triple checked the server IP in:

-Litespeed > General

-QC > Settings

-At my web host

It is the same IP in all those three places.

This is what I have done since you helped me last time (because I wanted a fresh connection between Litespeed and QC after having done many changes to my site, including moving to different servers, since I first made the connection):

-Deleted my domain in QC

-Clicked on “Remove Quic Cloud data” in Litespeed > CDN

-Request new domain key in Litespeed > General

-Reconnect Litespeed to Quic Cloud by going through the automatic CDN installation

-Removing AAAA record from QC > DNS Zone

It is strange, because there was some UCSS and CCSS files uploaded to QC right after I reconnected Litespeed/QC, and since then 1 CCSS file has been uploaded every day. But there were more than 100 files in queue when I ran the queues manually, so something is not working right.

-Does it make a difference if I use the crawler to fill the UCSS/CCSS queues, compared to if I manually visit the pages of my site to fill the queues?

-In the QC DNS zone, there are 4 different A-records (listed below):

1: *

2: @ (CDN enabled)

3: ftp

4: www

Should there be only one A-record, and could this be causing issues?

Thank you!

em, please try create a file , name it like test.php with code:

<?php

require_once('./wp-load.php');

if (!class_exists('LiteSpeed\Crawler')) {
    die('something wrong');
}

use LiteSpeed\Crawler;

$crawler = new Crawler();
$url = 'https://specialplasticparts.com/produkt/dorrskylt-paminnelse-larm';
$ua = 'lscache_runner';
$uid = false; 
$accept = false;

$response = $crawler->self_curl($url, $ua, $uid, $accept);

var_dump($response);

open it in browser, see what it returns

Hello,

I am not so good at these things, please check if I did it right:

-I created the file in public_html for my site

-I opened my site in a browser using this address: https://specialplasticparts.com/test.php

The result was: bool(false)

yeah… that should not be this result , but the page content

please provide me the latest report , let me double check your setting.

Rapportnummer: KKBYIROJ

[root@v220221044927204975 ~]# curl -I -XGET --resolve specialplasticparts.com:443:__.__.38.219 https://specialplasticparts.com/produkt/dorrskylt-paminnelse-larm/
HTTP/2 404
content-type: text/html
last-modified: Tue, 19 Mar 2024 20:16:14 GMT
etag: "999-65f9f28e-b92afb42c42860cb;;;"
accept-ranges: bytes
content-length: 2457
date: Mon, 05 Aug 2024 13:15:30 GMT
server: LiteSpeed
location: https://specialplasticparts.com/index.php
platform: hostinger
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"

the __.__.38.219 is the origin IP ?

it is indeed giving 404 error response on that URL

Hello and thank you for your support!

I contacted my web host, and these are the answers I got (I will paste their answers below):

-Yes, __.__.38.219 is the origin server IP

-It is technically impossible to visit a website at IP address 77.37.38.219, as it is not supported on Web, Cloud and WordPress hosting. Access to the site by IP address is only possible on a VPS server.

-I can confirm that __.__.38.219 is the original IP address of your server, however, this IP address responds with 403 error due to access restriction, this does not affect the availability of your website. It is technically impossible to access the website using the IP address for this hosting plan.

-I checked it further and this is what I did, I tested your server IP. It shows that your server is responsive. Now it is not possible to reach your server IP through URL, because you are not using VPS server. Only VPS users can reach their website via URL, that’s why access to it is denied ?? In this case I would highly suggest you to contact quic cloud again and explain to them that you’re using shared hosting and that is the reason why they cannot access server via URL, but I can see that your website is totally responsive and works perfectly fine ??

then in General -> Server IP , you need to set an IP that is public accessible, where it gives normal content instead of 404

Hello,

I checked again with my web host, and this is what they say:

“I checked it further and I would like to point out that your server IP is responsive and publicly available. Also I checked it further and I would highly recommend you to check this article here:

https://docs.quic.cloud/onboarding/enable/

Also, I can see that your LiteSpeed plugin (from Quic CLoud) is working perfectly fine.

Now in this case you should ask where you set it up correctly in the WordPress and to be specific in this LiteSpeed plugin, since there is nothing wrong from our side and your website is fully responsive ??”

It is technically impossible to visit a website at IP address 77.37.38.219

this is actually kind of wrong …

How do you mean when you say “wrong”?

Do you mean that it should not be that way?

Or do you mean that the statement is incorrect, and that it is actually possible to visit the IP address?

let’s try this other way around

please go bypass the QC CDN , wait for 10 – 20 minutes, then open that link , see what it returns

I bypassed CDN and waited 30 minutes.

Then revisited the page https://specialplasticparts.com/test.php in a private browser.

The content of the page is still:

bool(false)