Inlining CSS Causes Homepage Header to Return 500, but Page Loads Fine

  • Resolved C13

    (@c13creative)


    4 years, 3 months ago

    Today I noticed that Google isn’t seeing my homepage because the page returns a 500 error, even though it loads completely fine to visitors. After a bunch of debugging, I found Critical CSS to be the culprit, and I was able to repeat the issue with “Inline all CSS”. Here are the strange behaviors:

    • The issue is only on my assigned homepage. If I change my homepage to a blank page, the error is now on that page and no longer on the original homepage.
    • The issue goes away when I disable “Inline and defer”/”Inline all CSS”.
    • The issue does not go away when I switch to a default WordPress theme. theme.
    • The issue does not go away when I disable all other plugins.
    • The issue does not go away when I remove all code under “Customize” > “Additional CSS”.

    Does AO add anything to the homepage when inlining CSS that could cause a 500 error? Any idea what could be causing the bug?

    I will likely keep the bug live tonight while I continue troubleshooting but will have to disable inline CSS by tomorrow.

    Thank you.

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    Crazy bizarre, even more so because when visiting the page it works visually, but the response indeed is a HTTP500 even for me (and probably other visitors);

    Do you have a staging site and if so does it happen on that one as well?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    Oh, forgot to ask; any relevant PHP errors in the PHP-errorlog-file?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    OK, when requesting the page with a querystring added to the URL, it does not return a HTTP 500 errors;

    Adding a querystring makes Comet Cache not caching the page (or serving it from cache), adding this comment at the bottom of the HTML;
    <!-- Comet Cache is NOT caching this page, because$_GETcontains query string data. The current configuration says NOT to cache GET requests with a query string. -->

    So the question; have you tested with Comet Cache disabled?

    Thread Starter C13

    (@c13creative)

    FIXED IT.

    I messaged my host a little while ago because I was not seeing any 500 error logs. They sent me this error message:

    ModSecurity: Output filter: Response body too large (over limit of 524288, total not specified). [hostname "clubgsl.com"] [uri "/index.php"]

    I disabled ModSecurity in cPanel and everything is working again. But I have no idea why inlining CSS on my homepage would cause ModSecurity to think the response is gigantic, even when I disable all plugins, make the homepage a blank page, and switch to the Twenty Twenty theme. And only on this WP installation; I have a few other very similar WP setups on the same server and they don’t have any issue.

    At least it’s working. Thank you and the entire AO team for all your hard work.

    Thread Starter C13

    (@c13creative)

    And I did test it with CometCache disabled. Perhaps you tried adding the querystring right after I disabled ModSecurity?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    could be yes ??

    happy all is fine now! feel free to leave a review of the plugin and support here! ??

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Inlining CSS Causes Homepage Header to Return 500, but Page Loads Fine’ is closed to new replies.