I am running a WPML site which is constantly giving random Litespeed 404 errors. It happens on various pages, and then resolves after some time. It seems to happen only on pages that are not the default language. Also, other pages will load while other give a 404.
To enable it, open your wp-config.php file and look for
define('WP_DEBUG', false);
Change it to:
define('WP_DEBUG', true);
// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);
// Disable display of errors and warnings
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
After this, repeat the action that causes the problem on your site (the 404 error). The errors will be saved to a debug.log log file inside the /wp-content/ directory. Then please share the errors with me.
Our second-tier supporter is still not sure why this problem happens. He says that in the header, he sees the server response coming from CloudFlare. So, Perhaps this is the issue – combining Cloudflare with Lightspeed cache.
Could you please temporarily deactivate the LiteSpeed cache plugin and check if the problem persists?
I would appreciate it if there is any way to escalate / expedite support on this issue.
We are running a time-sensitive public-awareness campaign with wide media support and it's really tragic every day that this error impacts our audience.
Please also try the following on the staging site.
I suspect that there is a collision with the theme or another plugin that might cause this problem. If possible, get your site into a minimum environment. A minimum environment means switching to a default WordPress theme like TwentyTwenty-One and no plugins activated except WPML.
First, you will need to check if the problem persists when just the theme is switched to TwentyTwenty-One (for example). If it persists, then deactivate all plugins except the WPML and its add-ons. Then please check if the problem persists. If it does not persist, start by activating the plugins one by one and check when the problem comes back, then report to me which was the culprit plugin.
**** Important! Please make a full site backup (files and DB) before you proceed with those steps****
*** If your site is live, you might want to try those procedures in a staging environment or a snapshot of your site on your local server or another server. ***
If the above does not help, please share with us access to your site. I'm enabling a private message for the following reply. Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
After extensive testing, it appears that two separate plugins are both conflicting with WPML:
PixelYourSite and WP Activity Log
If either or both are active then WPML quickly throws a 404 on any non-default language page (like whatever.com is always fine but whatever.com/en/ would quickly fail).
Now that both plugins are disabled, the site appears to be stable, but we will continue testing. We will also need to find a replacement method for injecting the FB Pixel. The Activity Log we can live without.
I'm confused. On your staging site, I don't see this problem now. I also checked your live site, switched between languages and pages, and I don't get the 404 error as I could see yesterday.
1. Where do you get the random 404 error on the staging or live site?
2. You said that you found that the WP Activity Log and PixelYourSite plugins are the culprits. But it is unclear to me if you still get the 404 errors when these two plugins are deactivated.
Those plugins had an immediate effect on the frequency of 404's. Both are now disabled on live and staging. However, the live site is still suffering random 404's.
You can easily trigger the issue by rapidly switching between /en/ and /fr/ versions of the site. I usually get the error after about 10 reloads.
One clue seems to be that when the 404 comes up, regenerating permalinks seems to solve the problem immediately. The site will then work for me for about 10 page reloads between the different languages before failing again.
Hi, and thanks for sharing the video and the links.
I've tried what you suggested and showed on the video. I constantly switched between pages and languages for more than one minute, and I didn't get the 404 error even once.
Did you add the suggested code from the errata page?
To enable it, open your wp-config.php file and look for
define('WP_DEBUG', false);
Change it to:
define('WP_DEBUG', true);
// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);
// Disable display of errors and warnings
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
After this, repeat the action that causes the problem on your site (the random 404 errors). The errors will be saved to a debug.log log file inside the /wp-content/ directory. Then please share the errors with us.
Thanks,
Itamar.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
