Conversation
supportCookie banner shows twice to visitors. No matter if you accept it or not, when you enter another page or refresh it, the cookie banner will show again. But if yoou accept it twice, then it will work. The page I need help with: [ log in to see the link]
Hello, We are sorry for the inconvenience caused. We looked at your website and found that, the cached version of your pages are older than 24 hours, which means that the nonce on those pages are all invalidated. Nonce are random characters which are used for Security in WordPress and they have maximum lifetime of 24 hours and those nonce need to be refreshed, as the cache is older than 24 hours the nonce got invalidated. So when CookieAdmin sends a request to the backend of your website with that nonce, it returns error, as the nonce got invalidated. Please try deleting the cache and let us know if you still face the same issue, and we suggest you set the cache life span of around 12-15 hours, that will keep the nonce on your pages fresh. Regards, Vardan
I have no idea what you have just written. Does your plugin has a problem with Litespeed Cache? Because it is the first time I have used it. All other websites I have build use CookieYes and that one has no problem with cache at all.
Hi, Thank you for bringing this to our attention. To explain this in simple terms: CookieAdmin saves the user’s consent by sending a secure request to WordPress in the background. On sites using very aggressive caching (like LiteSpeed), the security token used to save consent expires. As a result, the cookie banner appears again and accepting it a second time works because a fresh page is then served. What you can do right now: 1. Add CookieAdmin consent cookie to the “Do Not Cache Cookies” in LiteSpeed Cache. 2. OR Reduce the lifetime of cache, so pages refresh before the cache expires. We understand this is not ideal, and we are actively reviewing improvements to make CookieAdmin more cache-friendly so this does not happen in future versions. Please open a support ticket with our team at support@cookieadmin.net , and we’ll be happy to provide you with step-by-step instructions for LiteSpeed.
I understand the technicalities of this. I just want to know whether you are going to fix it and whether your plugin has problems with Litespeed cache. If you your solution is to exclude the cookie from cache, then give me the specific cookie filename to exclude.
Hi. Thank you for your co-operation. Yes, we do intend to address this behavior so that CookieAdmin works reliably by default across cached environments. As a temporary mitigation, the most balanced approach with LiteSpeed Cache is to limit how long cached pages are kept, so that those tokens are refreshed automatically. Temporary LiteSpeed setting: 1. Go to LiteSpeed Cache → Cache → TTL 2. Set Default Public Cache TTL to: 43200 This ensures cached pages are regenerated (every 12 hours) before the nonce expires, reducing the likelihood of consent save failures, while still allowing caching to function normally. We appreciate your patience and the insight you’ve shared.
You’re not alone with this issue. Based on my experience, I would recommend disabling LiteSpeed Cache until CookieAdmin releases a proper fix. That’s ultimately what I had to do as well. Reducing cache TTL can reduce how often the problem appears, but it doesn’t actually resolve it. Likewise, adding “consent” to Do Not Cache Cookies in LiteSpeed Cache does not fix the issue either, I tested that and several other combinations without success. Until the nonce handling is fixed properly, LiteSpeed caching and CookieAdmin don’t seem to coexist reliably in this scenario.
Hi. Apologies for the inconvenience. We understand your situation and value your feedback. We are actively making changes to make CookieAdmin more cache-safe going forward, so that it works reliably without requiring users to weaken their caching setup. The version with this changes should be available by the end of this week. In the meantime, we recommend cache adjustments only as a temporary measure, not as a permanent requirement. This reply was modified 3 months, 3 weeks ago by maheshmi .
Hi, Thank you for being patient. We have launched CookieAdmin v1.1.5, which should fix the nonce issue and added new features : https://wordpress.org/plugins/cookieadmin/#developers Please update CookieAdmin, if you haven’t and let us know if you have any queries.
What specifically have you chaned to adress the issure I reported? Is it now compatible with Litespeed Cache? Does it work with default cache setting? What difference should I see now?
Hello, You won’t face the issue you were facing earlier, of consent re-appearing after the preference was saved. We have made changes such that cache won’t have any affect on saving of Cookie banner preference. So it is compatible with LiteSpeed Cache. Let us know if you have any query or if you still face the same issue. Regards, Vardan
Hello, We are sorry for the inconvenience caused. We looked at your website and found that, the cached version of your pages are older than 24 hours, which means that the nonce on those pages are all invalidated. Nonce are random characters which are used for Security in WordPress and they have maximum lifetime of 24 hours and those nonce need to be refreshed, as the cache is older than 24 hours the nonce got invalidated. So when CookieAdmin sends a request to the backend of your website with that nonce, it returns error, as the nonce got invalidated. Please try deleting the cache and let us know if you still face the same issue, and we suggest you set the cache life span of around 12-15 hours, that will keep the nonce on your pages fresh. Regards, Vardan
I have no idea what you have just written. Does your plugin has a problem with Litespeed Cache? Because it is the first time I have used it. All other websites I have build use CookieYes and that one has no problem with cache at all.
Hi, Thank you for bringing this to our attention. To explain this in simple terms: CookieAdmin saves the user’s consent by sending a secure request to WordPress in the background. On sites using very aggressive caching (like LiteSpeed), the security token used to save consent expires. As a result, the cookie banner appears again and accepting it a second time works because a fresh page is then served. What you can do right now: 1. Add CookieAdmin consent cookie to the “Do Not Cache Cookies” in LiteSpeed Cache. 2. OR Reduce the lifetime of cache, so pages refresh before the cache expires. We understand this is not ideal, and we are actively reviewing improvements to make CookieAdmin more cache-friendly so this does not happen in future versions. Please open a support ticket with our team at support@cookieadmin.net , and we’ll be happy to provide you with step-by-step instructions for LiteSpeed.
I understand the technicalities of this. I just want to know whether you are going to fix it and whether your plugin has problems with Litespeed cache. If you your solution is to exclude the cookie from cache, then give me the specific cookie filename to exclude.
Hi. Thank you for your co-operation. Yes, we do intend to address this behavior so that CookieAdmin works reliably by default across cached environments. As a temporary mitigation, the most balanced approach with LiteSpeed Cache is to limit how long cached pages are kept, so that those tokens are refreshed automatically. Temporary LiteSpeed setting: 1. Go to LiteSpeed Cache → Cache → TTL 2. Set Default Public Cache TTL to: 43200 This ensures cached pages are regenerated (every 12 hours) before the nonce expires, reducing the likelihood of consent save failures, while still allowing caching to function normally. We appreciate your patience and the insight you’ve shared.
You’re not alone with this issue. Based on my experience, I would recommend disabling LiteSpeed Cache until CookieAdmin releases a proper fix. That’s ultimately what I had to do as well. Reducing cache TTL can reduce how often the problem appears, but it doesn’t actually resolve it. Likewise, adding “consent” to Do Not Cache Cookies in LiteSpeed Cache does not fix the issue either, I tested that and several other combinations without success. Until the nonce handling is fixed properly, LiteSpeed caching and CookieAdmin don’t seem to coexist reliably in this scenario.
Hi. Apologies for the inconvenience. We understand your situation and value your feedback. We are actively making changes to make CookieAdmin more cache-safe going forward, so that it works reliably without requiring users to weaken their caching setup. The version with this changes should be available by the end of this week. In the meantime, we recommend cache adjustments only as a temporary measure, not as a permanent requirement. This reply was modified 3 months, 3 weeks ago by maheshmi .
Hi, Thank you for being patient. We have launched CookieAdmin v1.1.5, which should fix the nonce issue and added new features : https://wordpress.org/plugins/cookieadmin/#developers Please update CookieAdmin, if you haven’t and let us know if you have any queries.
What specifically have you chaned to adress the issure I reported? Is it now compatible with Litespeed Cache? Does it work with default cache setting? What difference should I see now?
Hello, You won’t face the issue you were facing earlier, of consent re-appearing after the preference was saved. We have made changes such that cache won’t have any affect on saving of Cookie banner preference. So it is compatible with LiteSpeed Cache. Let us know if you have any query or if you still face the same issue. Regards, Vardan