You have too many requested images, please try again in a few minutes.

Hi,

May I know what is your domain ?

and please also make sure your REST API is working properly

Best regards,

The page I have troubles with, is mentioned in the original post (having a hard time posting links in messages as it looks spammy).

Doing the REST diagnostics I get this result

{"_res":"ok"}

On the FAQ page mentioned, it says

“Check the last part of the string that is returned. It should say “status”:404.”

so I’m actually a bit in doubt whether the status I get is ok…

If I disable the Litespeed Cache plugin entirely, I DO get the status 404, but I’m obviously unable to perform any image optimizations with the plugins disabled.

Lastly, the FAQ mentions that

Also, please take a look at your rewrite rules in .htaccess. If you have a rule that ends in [L] it must not appear before the WordPress section, or else the WordPress rules will never be processed, and the REST API request will result in failure.

But the following code in htaccess, which appears to be inserted by LiteSpeed before the WordPress rules, includes a rule ending in [L], so I’m really very much in doubt of what to make of this:

# BEGIN NON_LSCACHE
## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
### marker Network CSS/JS Auto Generation Rules start ###
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !^/wp-content
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-content/litespeed/cssjs/.*) $2 [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} ^/wp-content/litespeed/cssjs/.+\.(css|js)$
RewriteRule . /index.php [L]
### marker Network CSS/JS Auto Generation Rules end ###
## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
# END NON_LSCACHE

Please let me know if I can provide you with further details to get to the bottom of this.

Bjarne

Hello,
I am having the same issues as Bjarne.
Also have the same L in htaccess.

Looking forward to the response!

I’ve now “rebuilt” the htaccess entirely, by deleting it and pasting in the core WordPress as mentioned in the WordPress multisite “root site” settings.

So the htacces now only includes core and LiteSpeed rules. Still the same error.

I then tried to move the LiteSpeed rules BELOW the core WordPress rules, making my htaccess look like below, and waiting for the 5 minute cooldown …

Still not working.

Nothing is being pulled, and the pull button never gets enabled.

I’m out of ideas.

# BEGIN WordPress
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
# END WordPress

# BEGIN LSCACHE
## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
<IfModule LiteSpeed>
RewriteEngine on
CacheLookup on
RewriteRule .* - [E=Cache-Control:no-autoflush]
RewriteRule \.object-cache\.ini - [F,L]

### marker CACHE RESOURCE start ###
RewriteRule wp-content/.*/[^/]*(responsive|css|js|dynamic|loader|fonts)\.php - [E=cache-control:max-age=3600]
### marker CACHE RESOURCE end ###

### marker FAVICON start ###
RewriteRule favicon\.ico$ - [E=cache-control:max-age=86400]
### marker FAVICON end ###

### marker DROPQS start ###
CacheKeyModify -qs:fbclid
CacheKeyModify -qs:gclid
CacheKeyModify -qs:utm*
CacheKeyModify -qs:_ga
### marker DROPQS end ###

</IfModule>
## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
# END LSCACHE
# BEGIN NON_LSCACHE
## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
### marker Network CSS/JS Auto Generation Rules start ###
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !^/wp-content
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-content/litespeed/cssjs/.*) $2 [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} ^/wp-content/litespeed/cssjs/.+\.(css|js)$
RewriteRule . /index.php [L]
### marker Network CSS/JS Auto Generation Rules end ###
## LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! ##
# END NON_LSCACHE

• This reply was modified 3 years, 12 months ago by Bjarne Oldrup. Reason: typo

Hello,

I enabled Lazy loading in Media settings. Now i see its optimizing images.
I suppose this doesn’t have anything to do with it. Could you verify the same Bjarne?

Further troubleshooting info:

1. I have two other very similar configured sites on the same host, on both sites, LiteSpeed Image Optimization works fine, both manual and auto (cron)
2. One of the sites I updated to PHP 8.0.2, testing manual optimization afterwars, works fine

Leaving me with the suspicion that this issue, at least in my case, has something to do with the site being a multisite (networked).

Hi,

from server side , I can see it warns about wrong domain key

please try refresh the domain key

and then go to QC dashboard -> domain -> setting -> click “Having troubles connecting the LSCWP plugin with QUIC.cloud?” –> it will display a string , in format like XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX mixed by upper case letters and numbers , note it down somewhere

then go to toolbox -> report -> in “System Information” field , looking for “api_key” , and see if both string are matched

Best regards,

Thanks for looking into this!

I’ve reset and reconnected several times while troubleshooting, that maybe why the server warned about wrong domain key.

– Current API key, ending in A344, is the same in both QC Dashboard and Toolbos > Report > System info…

– I pushed the Send Optimization Request 10 minutes ago, and according to the QC Image Optimization Overview, one image has been processed a few minutes ago. The Pull button is still greyed out. Retried with another request. Same thing. So the Site > QC communication seems to be working, just not the other way around.

– I’ve send a LiteSpeed Report with Report number: NIJAQHCG – don’t know if that might shed more light over this issue.

– The website IS for testing purposes, and I can provide access with DoLoginSecurity if you think that could help.

Again, compression works on two other sites on the same host with similar configurations, besides this one being a multisite.

Kind regards
Bjarne

Hi,

please create a ticket by mail to support at litespeedtech.com

we will investigate it further

Best regards,

Hey!

Thank you for the offer. But I really think, I should create a new multisite installation to test on first, before I and you spend more time on this issue. After all, the site in question, is a test site with a lot of plugins, and since I have four other sites using litespeed image compression just fine, hosted on two different hosts, I must say, I have a nagging suspicion that this particular bug is crawling around on my end.

I’ll close this for now, and should I be able to reproduce the issue on a new site, I’ll get in touch.

Thank you for your patience.
Bjarne