Wordpress LScache Plugin: Login Nonce Conflict
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hello, While LiteSpeed ??plugin is active and when I try to log in from upper right corner, I encounter with a conflict because: $_POST[ wpqa_login_nonce ] and wp_create_nonce( wpqa_login_nonce ) is not the same. I understand that $_POST[ wpqa_login_nonce ] is cached and obsolete. How can I solve this problem with the best efficiency without using ESI, because using it is creating other problems.. My best solution is to make the Default Public Cache TTL time to 12 hours. But it is also not efficient. Do we have any other option, like exclude just this process from caching, or exclude $_POST[ wpqa_login_nonce ] from caching?` The page I need help with: https://hubyr.com/ Hello @bad0 Technically the options you suggested are possible, but I dont think our devs will implement this soon. If you want a different TTL for that block, currently ESI shortcode block could set separate TTL. Can you consider a work-around with that? Please refer to this: https://docs.litespeedtech.com/lscache/lscwp/admin/#turning-wordpress-shortcodes-into-esi-blocks Regards, Abe Hello Abe, In order to use this technique, I must enable ESI from LiteSpeed settings, right? Hi, yes, you must enable ESI and also use one of the following : LiteSpeed webserver, LiteSpeed ADC or QUIC cloud CDN , as OpenLiteSpeed doesnt have ESI feature Best regards, `Hello, If I enable ESI, it is creating different major problems in the theme. So is there any other option that I do not use ESI? Best regards.. I experience the same problem with the logout process by the way. It directs me to wp-die-message , which says are you really want to log out from xxx ? Hi, well , if ESI is not option , then only alternative way is to set TTL to lower , like 8 , 10 or 12 hours Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference