Critical Css not generated

Also, the last time ccss was generated was on 20/04/2019, which was when I was playing with it and decided to activate it. I had the same problem when testing but then after clicking a few times on “run the queue manually”, it did work once.

Thank you, but as I explained in my first post, even when the option to create ccss in the foreground is selected, ccss does not seem to be generated, FOUC still happens after visiting the page more than once, why is this?

Check out this page: https://nomadicboys.com/contact-nomadic-boys/
(or any other page actually), ccss is not being generated, it shows empty
<style id=”litespeed-optm-css-rules”></style>

Also, whenever I click on one of the menu options under Litespeed plugin, I get the following error message: “Failed to post via WordPress: Please try later”

I have the debug log file already:

04/22/19 10:15:01.875 [109.110.246.162:64422 1 lZy] [CSS] cron job [type] page-3efaa37937e376df90103b0a905a13cc [url] https://nomadicboys.com/about-nomadic-boys [UA] Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36 Google Favicon
04/22/19 10:15:01.879 [109.110.246.162:64422 1 lZy] [CSS] Generating: — array (
‘home_url’ => ‘https://nomadicboys.com&#8217;,
‘url’ => ‘https://nomadicboys.com/about-nomadic-boys&#8217;,
‘ccss_type’ => ‘page-3efaa37937e376df90103b0a905a13cc’,
‘user_agent’ => ‘Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36 Google Favicon’,
‘is_mobile’ => 0,
)
04/22/19 10:15:01.880 [109.110.246.162:64422 1 lZy] [IAPI] posting to : https://us.wp.api.litespeedtech.com/ccss
04/22/19 10:15:01.943 [109.110.246.162:64422 1 lZy] [IAPI] failed to decode post json: Please try later
04/22/19 10:15:01.945 [109.110.246.162:64422 1 lZy] [CSS] empty ccss
04/22/19 10:15:01.945 [109.110.246.162:64422 1 lZy] [CSS] cron job [type] default [url] https://nomadicboys.com [UA] Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36
04/22/19 10:15:01.945 [109.110.246.162:64422 1 lZy] [CSS] Generating: — array (
‘home_url’ => ‘https://nomadicboys.com&#8217;,
‘url’ => ‘https://nomadicboys.com&#8217;,
‘ccss_type’ => ‘default’,
‘user_agent’ => ‘Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36’,
‘is_mobile’ => 0,
)
04/22/19 10:15:01.946 [109.110.246.162:64422 1 lZy] [IAPI] posting to : https://us.wp.api.litespeedtech.com/ccss
04/22/19 10:15:05.083 [109.110.246.162:64422 1 lZy] [IAPI] failed to decode post json: Please try later
04/22/19 10:15:05.084 [109.110.246.162:64422 1 lZy] [CSS] empty ccss
04/22/19 10:15:05.084 [109.110.246.162:64422 1 lZy] [CSS] cron job [type] search [url] https://nomadicboys.com [UA] Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

the option “Failed to post via WordPress: Please try later” is triggered when I try to run the critical css queue manually (when the option critical css is generated in the background)

Please also note, I disabled all other plugins until I had only Litespeed only.