generate Critical CSS failed

  • jvande

    (@jvande)


    2 weeks ago

    Complete error message, some pages were regenerated, this one repreatedly fails:

    Cornerstone page

    Something went wrong, which Jetpack Boost did not anticipate. An unexpected error occurred while trying to generate Critical CSS for the following page:

    Please follow the troubleshooting steps below for the page.

    1. 1Visit the page.
    2. 2Verify that the page loads correctly.
    3. 3If it does, try again to generate the Critical CSS.
    4. 4If the error still persist please contact Jetpack Boost Support↗ with a copy of your error message.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Josh (a11n)

    (@vitkory)

    1 week, 5 days ago

    Howdy @jvande,

    Thanks for reaching out and for including the error details.

    Since this is happening on a staging site (staging.actonexchange.org), the most likely cause is an access restriction preventing the Critical CSS generator from reaching the page. The generator needs to fetch your pages to analyze the CSS, so if the staging environment has any of the following, it won’t be able to complete:

    • HTTP authentication (username/password prompt)
    • IP allowlisting or firewall rules
    • A “coming soon” or maintenance mode plugin
    • The site not being publicly accessible

    Could you confirm whether your staging site is publicly accessible? Try opening staging.actonexchange.org in a private/incognito browser window (while logged out) and see if the homepage loads without any login prompts or blocks.

    If the staging site is intentionally restricted, Critical CSS generation won’t work there. You’d either need to temporarily open access while generating the CSS, or skip Critical CSS on staging and only use it on your production site.

    Let us know what you find and we can go from there.

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    9 hours, 57 minutes ago

    Hi there, @jvande,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

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

You must be logged in to reply to this topic.