Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter thewojtek

    (@thewojtek)

    OK, will try it once it goes official. Thank you!

    Thread Starter thewojtek

    (@thewojtek)

    Hi @tenkstars

    currently I got 14 css enqueued. Once I click “force cron” (God knows how many times I did it already) the LSCache Dashboard reloads (as expected) and 14 css qre still in queue. No trace of file creation in site files and no trace of activity in my quic.cloud dashboard as well (CSS Opt. 0%).

    The cron itself works OK, as LSCache image optimization works perfectly (I got some 16k images optimized in May and currently my quic.cloud shows 20% image optimization usage.

    I turned on the debug logging and while I am not sure I can read it, here’s what happens when I click “force cron”:

    06/24/21 19:49:44.458 [77.255.137.217:51092 1 Pxo] ?? ------GET HTTP/1.1 (HTTPS)  /wp-admin/admin.php
    06/24/21 19:49:44.458 [77.255.137.217:51092 1 Pxo] Query String: page=litespeed-page_optm&LSCWP_CTRL=css&LSCWP_NONCE=5236cf9361&litespeed_type=generate_critical
    06/24/21 19:49:44.459 [77.255.137.217:51092 1 Pxo] HTTP_REFERER: https://inisi.pl/wp-admin/admin.php?page=litespeed-page_optm
    06/24/21 19:49:44.459 [77.255.137.217:51092 1 Pxo] Cookie _lscache_vary: admin_bar:1;logged-in:1;role:99
    06/24/21 19:49:45.076 [77.255.137.217:51092 1 Pxo] [Router] LSCWP_CTRL: css
    06/24/21 19:49:45.077 [77.255.137.217:51092 1 Pxo] [Router] LSCWP_CTRL verified: 'css'
    06/24/21 19:49:45.077 [77.255.137.217:51092 1 Pxo] [Router] parsed type: generate_critical
    06/24/21 19:49:45.077 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] front [url] https://inisi.pl [UA] Mozilla/5.0 (Macintosh; Intel Mac OS X 10_16) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1 Safari/605.1.15
    06/24/21 19:49:45.086 [77.255.137.217:51092 1 Pxo] ?? Init
    06/24/21 19:49:45.098 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] tax [url] https://inisi.pl/kategoria-produktu/obuwie/sandaly [UA] Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
    06/24/21 19:49:45.108 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] 404 [url] https://inisi.pl/apple-touch-icon.png [UA] Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/601.2.4 (KHTML, like Gecko) Version/9.0.1 Safari/601.2.4 facebookexternalhit/1.1 Facebot Twitterbot/1.0
    06/24/21 19:49:45.117 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] product [url] https://inisi.pl/produkt/santorini-flora-dress-2 [UA] Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36 Edg/91.0.864.54
    06/24/21 19:49:45.125 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] archive [url] https://inisi.pl/sklep/page/5 [UA] Mozilla/5.0 (compatible; bingbot/2.0; +https://www.bing.com/bingbot.htm)
    06/24/21 19:49:45.132 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] attachment [url] https://inisi.pl/inisi-artemis-fy [UA] Mozilla/5.0 (compatible; bingbot/2.0; +https://www.bing.com/bingbot.htm)
    06/24/21 19:49:45.140 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] page [url] https://inisi.pl/kontakt [UA] Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.1 Safari/605.1.15
    06/24/21 19:49:45.148 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] front.mobile [url] https://inisi.pl ??  [UA] Mozilla/5.0 (iPhone; CPU iPhone OS 14_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.1 Mobile/15E148 Safari/604.1
    06/24/21 19:49:45.157 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] 404.mobile [url] https://inisi.pl/produkt/chalki ??  [UA] Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.90 Mobile Safari/537.36 (compatible; Googlebot/2.1; +https://www.google.com/bot.html)
    06/24/21 19:49:45.166 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] product.mobile [url] https://inisi.pl/produkt/kloto-haftowany-meander ??  [UA] Mozilla/5.0 (iPhone; CPU iPhone OS 14_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 Instagram 193.0.0.29.121 (iPhone12,1; iOS 14_4_1; pl_PL; pl-PL; scale=2.00; 828x1792; 299401192)
    06/24/21 19:49:45.175 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] archive.mobile [url] https://inisi.pl/sklep ??  [UA] Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.90 Mobile Safari/537.36 (compatible; Googlebot/2.1; +https://www.google.com/bot.html)
    06/24/21 19:49:45.185 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] tax.mobile [url] https://inisi.pl/kategoria-produktu/odziez/sukienki/page/2 ??  [UA] Mozilla/5.0 (iPhone; CPU iPhone OS 14_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 Instagram 193.0.0.29.121 (iPhone12,1; iOS 14_4_1; pl_PL; pl-PL; scale=2.00; 828x1792; 299401192)
    06/24/21 19:49:45.193 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] attachment.mobile [url] https://inisi.pl/foreveryoung21_094 ??  [UA] Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.90 Mobile Safari/537.36 (compatible; Googlebot/2.1; +https://www.google.com/bot.html)
    06/24/21 19:49:45.201 [77.255.137.217:51092 1 Pxo] [CSS] cron job [type] page.mobile [url] https://inisi.pl/kontakt ??  [UA] Mozilla/5.0 (Linux; Android 7.0;) AppleWebKit/537.36 (KHTML, like Gecko) Mobile Safari/537.36 (compatible; PetalBot;+https://webmaster.petalsearch.com/site/petalbot)
    06/24/21 19:49:45.209 [77.255.137.217:51092 1 Pxo] [Ctrl] 301 from https://inisi.pl/wp-admin/admin.php
    06/24/21 19:49:45.209 [77.255.137.217:51092 1 Pxo] [Ctrl] 301 to https://inisi.pl/wp-admin/admin.php?page=litespeed-page_optm
    06/24/21 19:49:45.210 [77.255.137.217:51092 1 Pxo] [Ctrl] X Cache_control -> no Cache ( 301 to same url )
    06/24/21 19:49:45.210 [77.255.137.217:51092 1 Pxo] [Ctrl] not cacheable before ctrl finalize
    06/24/21 19:49:45.210 [77.255.137.217:51092 1 Pxo] [Router] get_role: administrator
    06/24/21 19:49:45.211 [77.255.137.217:51092 1 Pxo] ?? X-LiteSpeed-Cache-Control: no-cache
    06/24/21 19:49:45.211 [77.255.137.217:51092 1 Pxo] [Optm] bypass: Not frontend HTML type
    06/24/21 19:49:45.211 [77.255.137.217:51092 1 Pxo] End response
    --------------------------------------------------------------------------------

    The above is with default loglevel, once I turn on “advanced” I can not find any mention of “litespeed_type=generate_critical” (which is, I assume, a sign of reaction to “force cron”) in the logs.

    Only two things catch my attention in advanced logging mode:

    06/24/21 20:00:25.624 [77.255.137.217:51693 1 Wl6] [Conf] Invalid option ID optm-ucss_whitelist
    06/24/21 20:00:25.698 [77.255.137.217:51693 1 Wl6] [Core] CHK html bypass: miss footer const

    I have honestly no idea how to proceed from there, though.

    • This reply was modified 3 years, 9 months ago by Yui.
    • This reply was modified 3 years, 9 months ago by thewojtek. Reason: added more logs
    Thread Starter thewojtek

    (@thewojtek)

    OK. It displays a HTML page indeed. Where in WordPress should I look to try and solve this issue? Apparently it is still something in my configuration.

    Thread Starter thewojtek

    (@thewojtek)

    Reopening, as still no go with Litespeed Cache.

    The result of calling https://wojtek.jakobczyk.org/wp-json/litespeed/v1/token is:
    {"_res":"ok"}

    Still, I disabled WP Cerber Security, there is no trace of anything that could be blocking API calls in wp-config.php as well.

    While I am behind cloudflare, all the IPs are bundled into an “allow” rule in CF firewall. CF reports “No firewall events found matching your filters” anyway.

    I do however have a few API calls saved in REST API LOG plugin:

    Date: 2021-03-12 00:51:43
    Source: WP REST API
    Method: POST
    Status: 200
    Elapsed Time: 1,443ms
    Response Length: 150
    User:
    IP Address: 188.68.46.236

    Request headers:

    {
        "accept": "*\/*",
        "content_type": "application\/x-www-form-urlencoded",
        "content_length": "4",
        "host": "wojtek.jakobczyk.org",
        "user_agent": "curl\/7.29.0"
    }

    Response headers:

    {
        "Content-Type": "application\/json; charset=UTF-8",
        "X-Robots-Tag": "noindex",
        "Link": "<https\/\/wojtek.jakobczyk.org\/wp-json\/>; rel="https\/\/api.w.org\/"",
        "X-Content-Type-Options": "nosniff",
        "Access-Control-Expose-Headers": "X-WP-Total, X-WP-TotalPages, Link",
        "Allow": "POST, GET",
        "Access-Control-Allow-Headers": "X-WP-Nonce"
    }

    Response body:

    {
        "data": {
            "_res": "err",
            "_msg": "lack_of_param"
        },
        "headers": {
            "Allow": "POST, GET"
        },
        "status": 200
    }
    • This reply was modified 4 years ago by thewojtek.
    • This reply was modified 4 years ago by thewojtek.
    Thread Starter thewojtek

    (@thewojtek)

    Using:
    https://wojtek.jakobczyk.org/wp-json/litespeed/v1/ip_validate

    The response is:
    {"code":"rest_no_route","message":"Nie znaleziono routingu pasuj\u0105cego do adresu URL oraz metody zapytania.","data":{"status":404}}

    which is in line with the troubleshooting page.
    I went that far I disabled all plugins on the page apart from LiteSpeed.

    Removed absolutely everything apart from https redirect from my .htaccess and let LSCache write it’s data into it again.

    Still no go.

    • This reply was modified 4 years, 2 months ago by thewojtek. Reason: (added .htaccess edit)
    Thread Starter thewojtek

    (@thewojtek)

    By the love of god, logging out and logging back in seems to have solved the problem… Must have been something in the server or WP config I have messed up.

    Interestingly enough though, the “Logged out” event has not been logged.

    Thread Starter thewojtek

    (@thewojtek)

    No need to apologize, this is a free version after all… Yeah, this fixes the issue and keeps the theme good looking. Many, many thanks!

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