Wordpress LScache Plugin: Failed to communicate with LiteSpeed server: no auth_key
Last Updated on: Wed, 15 Apr 2026 00:00:02 This will also generate an API key from LiteSpeeds Server. API is creating this error! http://prntscr.com/hhtnnp and http://prntscr.com/hhtnwg The page I need help with: https://steroidsp.org Can you try again so we can get more log details? Looks like your server is doing a 301 redirect which broke the callback validation. I tried it again but unfortunately it gives an error. IAPI Error hash does not match: ClientCB[ 301 Moved Permanently < /title>< /head> 301< /h1> Moved Permanently < /h2> The document has been permanently moved.< /p> < /div>< /div> Proudly powered by LiteSpeed Web Server< /a>Please be advised that LiteSpeed Technologies Inc. is not a web hosting company and, as such, has no control over content found on this site.< /p>< /div>< /body>< /html> ] Server[JpPOBZqkxBXactG4] Bu mesaji gizle. Failed to communicate with LiteSpeed server: no auth_key The issue happens because you forced http to https ( maybe its a plugin? ), but your home url setting in WordPress is still http link. So the callback is redirected and failed to validate. Please correct your url setting in /wp-admin/options-general.php Oh yes.. htaccess delete http to https RewriteEngine On RewriteCond % HTTPS off RewriteRule ^(. )$ https://% HTTP_HOST % REQUEST_URI [L,R=301] and plugin disable https://wordpress.org/plugins/force-https-littlebizzy/ disable problem solved and http://prntscr.com/hhuouo this is not a valid solution Hi rifatozkan, It will work, but if you want to use https in the future, I will suggest you change Settings -> General -> WordPress Address (URL) and Site Address (URL) to https . It will become send and receive via https protocol. Best, Eric Based on https://wordpress.org/support/topic/litespeed-cache-image-optimization/page/2/#post-9744503 , we will release a fix on this. Also we added https on server side for your record. You should be able to do request again. Please try and let us know. thanks. This is fixed on our server side also. Change log will be in v1.6.6.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference