Wordpress LScache Plugin: Failed to post via WordPress: hash does not match: ClientCBerror code: 1020
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi there, I have read many topics on the support tickets but my issue still did not get solved. So, I thought to create a proper video to show you what the issue is and what changes I have tried to do to fix the issue but the issue did not get solved. I recorded my screen and upload the video on YouTube. Here is the video = https://youtu.be/OPZUa3X3QtM The domain of the website is [ redundant link removed ] and if you will need login details I will share it on [ email deleted ] if you say so or give any other mail. I have read this article before I am contacting you guys = https://wordpress.org/support/topic/failed-to-push-to-litespeed-iapi-server-hash-does-not-match-clientcbdoctyp/ What else I tried? I also tried HTTPS to HTTP but still, the same issue was showing. Errors: 1. Failed to post via WordPress: hash does not match: ClientCB[error code: 1020] Server[Pe6nJgWmVddVWRa7] 2. Failed to post via WordPress: no auth_key This topic was modified 2 years, 7 months ago by Jan Dembowski. Reason: Deleted email The page I need help with: https://ndaplumbingperth.com.au/ @daljitpattarsingh Please do not offer anyone access to your site and do not post your email address again. If the author or support for this plugin did take you up on that offer then they would risk having their plugin removed from WordPress.ORG. It is that serious. If they had asked for that login or replied to get that login away from these forums then this would be the reply to the author and plugin support person. While I know you have the best of intentions, its forum policy that you not ask users for admin or server access. Users on the forums arent your customers, theyre your open source collaborators, and requesting that kind of access can put you and them at high risk. If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums. Thankfully are other ways to get information you need: Ask the user to install the Health Check plugin and get the data that way. Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the users web server error log. Ask the user to create and post a link to their phpinfo() output. Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file. Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors). Ask the user for the step-by-step directions on how they can reproduce the problem. You get the idea. We know volunteer support is not easy, and this guideline can feel needlessly restrictive. Its actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, its difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline. When you help users here and in public, you also help the next person with the same problem. Theyll be able to read the debugging and solution and educate themselves. Thats how we get the next generation of developers. Reason: Formatting Hi, Could you please try v3 ? Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference