Generating UCSS failing 90% of the time due to curl timeout error

  • Resolved Jaro

    (@pixtweaks)


    3 years, 6 months ago

    Hi,
    I’ve got a one-page website and figuring out all CSS classes necessary to generate the correct UCSS.
    I’m having trouble generate UCSS after purging it. Most of the time it throws error:
    “Failed to request via WordPress: cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received [server] https://node449.quic.cloud [service] ucss”

    When I’m looking to Quic cloud, in the menu “Page Optimization (CCSS/UCSS) Overview”, tab “UCSS” it says in CPU column 37-40s, I presume it’s to generate my UCSS. https://screencast-o-matic.com/i/crQlocVQNlA

    I tried to change nodes but no difference.

    So I think that failed generation of my UCSS is because the curl has timeout 30s and generating UCSS takes 30+ seconds, so despite it been generated, curl stops and doesn’t receive the UCSS. Maybe it’s something else but can you please fix this?

    As well I had 30 seconds PHP execution time so it would fail anyway. I think this could cause problems for other users as well so maybe you can check if PHP execution time is long enough.

    In the end, can I offer a suggestion? UCSS is a great feature, but I think not every single URL need a unique CSS file. I would rather have UCSS based on a unique combined CSS file. Why? If I have a blog with 1000 posts, but each post has the very same CSS, UCSS will need to generate 1000 times the same UCSS. That’s not good if I need to purge UCSS after the update of a plugin or WP Core…

    Thank you for bringing this feature!

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hi,

    I assume your get the error from the debug logs on the plugin side. The problem is not that the UCSS isn’t generated. The problem is your plugin cannot pull the files from QC. What you see on your QC dashboard are the UCSS files already generated unless you see an error message. The “Timed out” error indicates your server security settings are blocking your plugin’s call to fetch the generated UCSS files from QC server Node449.

    Regards.

    Thread Starter Jaro

    (@pixtweaks)

    Hi @tenkstars,
    I don’t think it’s the server security that it’s blocking the fetching process of generated data. It’s the too long response for the too short timeout. The CSS amount used on the website (500Kb uncompressed) takes about 40 seconds to process but the plugin gave up fetching at the 30s mark. That’s either the timeout as server’s default for cUrl or the plugin assumes in its settings that 30 seconds would be enough. So I can’t do anything about that, it’s not a security/blocking issue on my server. It never happened on another website that has 20Kb of CSS. I think that’s a bug in fetching code. Can you please ask developers to review this issue. Thank you very much!

    Believe me I’ve resolved the same issue for a couple of users. You need to check and make sure your firewall is not blocking outgoing connection to our QC server. Here’s the list of the current IPs: https://quic.cloud/ips Should you still insist it is a bug in our plugin, please open up a ticket at our support site: https://store.litespeedtech.com/store/submitticket.php?step=2&deptid=2

    Regards.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Generating UCSS failing 90% of the time due to curl timeout error’ is closed to new replies.