faisalrony
Forum Replies Created
-
This is the final, conclusive, and disappointing update.
I followed your last advice to the letter. I performed the ultimate “clean slate” procedure:
- I re-installed the WordPress Core files using the “Re-install” button in the Dashboard.
- I completely deleted the LiteSpeed Cache plugin.
- I manually deleted all remaining LSC-related folders from my file system.
- I manually deleted all ‘litespeed.%’ entries from my database via phpMyAdmin to ensure it was 100% clean.
- Finally, I did a fresh, clean installation of the LiteSpeed Cache plugin from the WordPress repository and set it up.
The site worked for a few hours. I just checked now, and the exact same issue has returned. The plugin is disconnected, and all settings have been reset.
This is the ultimate, undeniable proof that the issue is not with my WordPress installation, my plugins, or my theme. The problem is 100% originating from the Namecheap hosting environment.
I want to thank you both for your extraordinary help, patience, and dedication. You have helped me gather the undeniable evidence I need to force my hosting provider to investigate their servers. I believe this ticket can now be closed, as there is nothing more we can do from the plugin’s side.
My apologies for the long silence. I have been conducting a thorough investigation following all the advice, and the results are truly baffling and conclusive.
Here is a summary of what I discovered:
- Duplicate Menu Mystery: As I mentioned, a duplicate “LiteSpeed Cache” menu item appears under my main “Settings” menu.
- Conflict Test – Plugins: I deactivated ALL plugins on my site, leaving only LiteSpeed Cache active. The duplicate menu item was still there. This proves no other plugin is causing the conflict.
- Conflict Test – Theme: Next, with all plugins still deactivated, I switched my theme to a default WordPress theme (Twenty Twenty-Four). Shockingly, the duplicate menu item was STILL THERE. This proves my theme is not the cause either.
- Final Check –
mu-plugins: I checked my/wp-content/directory via File Manager, and I can confirm that there is NOmu-pluginsfolder on my site.
Conclusion:
After eliminating every single possibility within my WordPress installation (plugins, theme, mu-plugins), we are left with only one conclusion: the issue is originating from my hosting environment (Namecheap) itself.Some server-side script or configuration at Namecheap is causing this duplicate menu to appear and is periodically resetting the plugin’s settings via
wp-cron.php.I am now completely convinced that this is a server-level issue that I cannot solve from my end. I will now contact Namecheap’s senior support team with all of this evidence.
Thank you both for your incredible expertise and patience. Your guidance helped me prove that the problem is not with the LiteSpeed plugin itself. I will let you know if I get a resolution from my host.
Hello @qtwrk,
Huge breakthrough! I have found the “smoking gun”!
Following your advice to search the files, I did a manual check of my directories and I found a rogue
litespeedfolder located directly inside/wp-content/, outside of the/plugins/directory.The correct plugin is located at
/wp-content/plugins/litespeed-cache/.This rogue
/wp-content/litespeed/folder is almost certainly the cause of all the problems, including the duplicate menu item and the settings being reset viawp-cron.php.Action Taken:
As a safe first step, I have renamed the rogue folder fromlitespeedtolitespeed_disabled.Current Status:
Interestingly, even after renaming the folder and purging all caches, the duplicate menu item under “Settings > LiteSpeed Cache” is still visible for now. However, I am confident that the conflicting code has been disabled.I believe we have finally found the root cause. What do you recommend as the final step? Should I now safely delete the
litespeed_disabledfolder?Thank you so much for guiding me to this discovery!
Hello @qtwrk,
I think I have found a major clue, possibly the root cause of the entire problem.
Before I performed the file search you suggested, I noticed something very unusual in my WordPress admin menu. There seem to be **two separate menu items for LiteSpeed Cache**.
1. The normal “LiteSpeed Cache” item on the main menu.
2. A second “LiteSpeed Cache” item nested inside the main “Settings” menu.
Please see this screenshot which clearly shows the duplicate menu items:
**[https://prnt.sc/IVMqwo6TGFo2]`**</p> <p>This is not normal, and it strongly suggests that I might have a duplicate or conflicting installation of the plugin, or another plugin is creating this extra menu item. This could explain why the settings are being reset by a
wp-cron.phpjob – perhaps the conflicting version is causing it.</p> <p>Given this new information, what do you recommend I do? Should I try to find and delete the duplicate plugin files from my/wp-content/plugins/directory?This feels like a huge breakthrough!
Hello @qtwrk,
**Update to my previous message:**
I have now downloaded and analyzed the server’s raw access log for the critical time window (September 11, 2025, between 22:45 and 22:50).
I found a very strong suspect. The
count.logshowed that the options were reset right before 22:50:03. In the access log for that exact period, I found the following entries:149.28.85.239 – – [11/Sep/2025:22:45:04 -0400] “GET /count.php HTTP/1.1” 200 0 “-” “Wget/1.19.5 (linux-gnu)”
167.88.61.211 – – [11/Sep/2025:22:48:17 -0400] “GET /terms-and-conditions/ HTTP/1.1” 200 63762 “-” “Mozilla/5.0 (iPhone; CPU iPhone OS 13_2_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Mobile/15E148 Safari/604.1”
45.32.67.144 – – [11/Sep/2025:22:50:07 -0400] “POST /wp-cron.php?doing_wp_cron=1757645407.8280720710754394531250 HTTP/1.1” 200 0 “-” “WordPress/6.8.2; https://goodhopemotors.com“
149.28.85.239 – – [11/Sep/2025:22:50:03 -0400] “GET /count.php HTTP/1.1” 200 0 “-” “Wget/1.19.5 (linux-gnu)”The
wp-cron.phpjob that ran at **22:50:07** seems to be the culprit. This confirms that a scheduled task is causing the reset.I am now waiting for your guidance on how to identify which specific task within
wp-cron.phpis causing this issue.Hello @qtwrk,
We have finally captured the event! The disconnection and settings reset happened, and I have not touched or fixed anything on the site yet. The problem is currently active.
I immediately checked the
wp-content/count.logfile. It clearly shows the exact moment when the options were wiped from the database. Here is the critical part of thecount.log:[2025-09-11 22:40:09] options count: 205
[2025-09-11 22:45:08] options count: 205
[2025-09-11 22:50:07] options count: 0
[2025-09-11 22:55:07] options count: 190
[2025-09-11 23:00:06] options count: 192As you can see, the options count dropped from **205 to 0** between **22:45 and 22:50 on September 11, 2025**.
Since I have not fixed anything, you can check the current state of the site. I am also downloading the server’s raw access log for this specific time window (
2025-09-11from22:45to22:50) to find any suspicious activity. I will post the relevant access log entries here shortly.This log is the “smoking gun” we were looking for. Based on this timestamp, can you guess what might have caused this?
Thank you for your brilliant strategy.
Thank you for the suggestion.
I have carefully reviewed my entire list of installed plugins, and I can confirm that I am not using any dedicated database optimization or cleanup plugins (like WP-Optimize, Advanced Database Cleaner, WP-Sweep, etc.). I also do not run any external database optimization scripts.
The only plugin that has some database maintenance features is Rank Math SEO, but I have not used its cleanup tools recently, and this issue has been occurring for a while. I don’t believe it is the cause.
So, the settings reset is happening without any obvious database cleaner running on the site.
Do you have any other ideas what could be causing this?
Thank you for your help.
Hello qtwrk,
Yes, that is exactly what I mean. All of the plugin’s settings get completely reset to their default values.
To be very clear, this is what happens every time:
- The connection to QUIC.cloud is lost, and the setup pop-up appears on the dashboard.
- All my previously configured settings are gone. For example:
- Guest Mode, which I had ON, gets turned OFF.
- Browser Cache, which I had ON, gets turned OFF.
- All my CSS and JS optimization settings (Minify, Combine, etc.) are turned OFF.
- My Image Optimization progress is reset to 0%.
- And on top of all that, the debug log box is also found empty.
So, it is definitely Case #1: the entire plugin’s settings are being wiped and reset. I have to re-import my settings from a backup file every time to fix it.
I hope this clarification helps.
Hello qtwrk,
This is an unbelievable update. The disconnection and settings reset issue has happened again.
However, even after we successfully reset the database options and confirmed that the debug log was working with a manual test, the debug log box in “Log View” is once again completely empty.
This confirms that whatever is causing the settings to reset is also preventing the debug log from being written or is deleting it entirely. The issue seems to be happening at a level that even the plugin’s debug function cannot capture.
I am completely at a loss for what could be causing this. The problem is clearly not with the plugin’s standard functionality but with some external factor on my hosting environment that is aggressively resetting the plugin’s data in the
wp_optionstable.Do you have any final ideas on what could be causing this from a server-side perspective? Could it be a specific cron job from the host, a security feature, or something similar?
Thank you for your extensive help so far.
Hello qtwrk,
Thank you for the confirmation. I have successfully reconnected to QUIC.cloud and have now manually reconfigured all my settings.
I have noted down the current date and time: 03 September, 2025 at 15.27
I will now monitor the site. If the disconnection happens again, I will check both the plugin’s debug log and the server’s access log for the relevant period and report back.
Thank you.
Hello qtwrk,
Excellent news! I have followed all your instructions, and the test was completely successful.
- I deleted the ‘litespeed.%’ options from my
wpnk_optionstable in phpMyAdmin. - I reconfigured the debug settings (Log ON, Level Advanced, URI includes
rest_route=/litespeed). - I visited the test URL (
/?rest_route=/litespeed/xxx). - I then checked the “Log View” tab, and this time, it is full of log data! The debug log is finally working correctly.
I am ready for the next step. What should I do now? Should I reconnect to QUIC.cloud and import my backed-up settings file?
Thank you so much for your expert guidance.
Hello qtwrk,
I have a critical update. The disconnection and settings reset issue has happened for the third time since I enabled debug logging.
Unfortunately, the result is the same as last time: **the debug log box in “Log View” is completely empty again**.
It seems that whatever is causing the settings to reset is also preventing the debug log from being written. The server’s access log shows successful connections from your bot, but the plugin’s own log remains empty.
This strongly suggests the issue might be happening at a level outside of the plugin’s direct control, possibly related to the server environment or a database issue.
Here is a fresh report number, generated immediately after this latest reset:
**Report Number: [DDJZTRQH]**
I have not yet reconnected the site or imported my settings, so the report reflects the “reset” state.
Given that the plugin’s debug log is not working, what would you suggest as the next diagnostic step?
Thank you.
Hello qtwrk,
Thank you for the guidance. I have downloaded the raw access log forgoodhopemotors.com (SSL)from my cPanel and searched for "rest_route".
I was able to find many entries. It seems the requests from the QUIC.cloud bot are reaching my server successfully. Here are some of the lines from the log:
65.108.104.232 - - [01/Sep/2025:10:17:39 -0400] "POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1" 200 23 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36"
65.108.104.232 - - [01/Sep/2025:10:23:21 -0400] "POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1" 200 23 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36"
65.108.104.232 - - [01/Sep/2025:10:31:04 -0400] "POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1" 200 23 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36"
65.108.104.232 - - [01/Sep/2025:10:33:47 -0400] "POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1" 200 23 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36"
65.108.104.232 - - [01/Sep/2025:10:35:10 -0400] "POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1" 200 23 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36"
103.72.163.222 - - [01/Sep/2025:10:37:01 -0400] "POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1" 200 23 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36"
65.108.104.232 - - [01/Sep/2025:13:18:14 -0400] "POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1" 200 23 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36"
65.108.104.232 - - [01/Sep/2025:13:28:40 -0400] "POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1" 200 23 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36"
65.108.104.232 - - [01/Sep/2025:13:57:16 -0400] "POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1" 200 23 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36"
As you can see, they all have a "200" status code.
Please let me know what this indicates and what our next step should be. Thank you.Hello qtwrk,
I have a very important update.
When the disconnection happens, it’s not just logging me out of QUIC.cloud. It is also completely resetting all of my LiteSpeed Cache plugin settings to their default values.
For example, Guest Mode turns OFF, Browser Cache turns OFF, all my CSS/JS settings are disabled, and my Image Optimization progress is reset to 0%. I have screenshots to prove this.
This means every time it disconnects, I have to re-import my settings from a backup file to get my site working correctly again.
The debug log is still active, and I have re-imported my settings for now. I will wait for the disconnection and reset to happen again and will capture the log for you as soon as it does. This seems to be a more serious issue than just a simple disconnection.
Thank you.
Hello qtwrk,
Thank you for your help. The disconnection issue happened again a short while ago.
Unfortunately, when I went to the “Log View” tab, the debug log box was completely empty. The “Copy Log” button did not copy anything, so I have no log to share at this time.
I have double-checked my settings in the “Debug Settings” tab, and everything is still configured exactly as you instructed (Debug Log ON, Level Advanced, URI includes
rest_route=/litespeed). I have saved the settings again and cleared the log viewer.I will now reconnect my site to QUIC.cloud and wait for the disconnection to happen again. I will share the log with you as soon as I can capture it.
Thank you for your patience.