@kowsar89 I had caching disabled on my WPO installation so I don’t think it has anything to do with cache preloading.
As far as NameCheap support, they’re useless. They told me to contact the plugin developer and have them “optimize” the plugin but can’t say what needs to be fixed or what is tripping the CPU overload. According to them, it’s not their job to review specific files or plugins for issues and “optimization.”
@amsgator This is unfortunate, I can recall a recent incident involving a hosting company (I’m not mentioning the name here) that reached out to us regarding WP-Optimize causing problems for one of their customers. They collaborated with us to address the issue. They conducted their own investigation in the interest of their customer and pinpointed the exact part of our codebase that was causing the conflict.
Cache preloading serves as just one example; there are other features that can be CPU intensive.
I have one more question, If you reset the WebP serving method from WP-Optimize, does it permanently resolve the issue? Here’s a screenshot demonstrating how to perform the reset: https://prnt.sc/tXxreDNwP-IE
Alternatively, if you disable the WebP feature, does it resolve the issue? I’m trying to narrow things down.
Assuming you’ve deactivated the plugin through the File Manager, I presume that reactivating it should not immediately trigger a 503 error. This should give you the opportunity to swiftly reset the WebP serving method before encountering the 503 error again.
I would greatly appreciate it if anyone could provide this piece of information. Thanks
@kowsar89 unfortunately the moment I activate the plugin my entire site goes down, front and backend. I’m not able to do anything at all to investigate.
I didn’t use any of the WPO features other than the database cleanup. Everything else was turned off.
Can anybody try the following steps and then activate the plugin to see if the issue is resolved?
- In your
wp-config.php file, add the following line:
define( 'WPO_USE_WEBP_CONVERSION', false );
- Delete the
.htaccess file from the “wp-content/uploads/” directory.
Additionally, I’m curious about the resource usage statistics from cPanel. Would someone be able to share that information? You can refer to this screenshot for guidance: https://prnt.sc/LFzIiEy-6WAG
Thanks
@kowsar89 that prevented it from throwing the 503. Also as a side note, simply adding the line to the wp-config.php works by itself. Deleting the .htaccess wasn’t necessary.
On a second side note, I’m using Shortpixel. I’m curious if anyone else is also and if that’s why disabling the webp conversion fixed the issue.
@kowsar89 when I enabled WPO, it created a new file in the uploads folder (wpo-plugins-tables-list.json). I’m not sure exactly what it does or if that helped fix the problem but I noticed the change.
Good to know that it worked; now we know where to look.
I doubt ShortpSixel is the cause since another user experiencing the same issue doesn’t even use ShortpSixel.
The wpo-plugins-tables-list.json file serves the purpose of identifying which plugin creates specific database tables within WP-Optimize’s Database Optimization page. It’s worth noting that this file is harmless and unrelated to the current issue.
@kowsar89 I did not use WPO for any image optimization. I’m not sure if what helps at all with where to start looking. It’s odd that it caused the issue when I didn’t even have it enabled.
@amsgator Since you’re interested, we conduct some checks to determine whether WebP conversion tools are available through your hosting or not. Depending on the results, we either display or hide the following option in settings: https://prnt.sc/W98LoCXGq7Zg
By define( 'WPO_USE_WEBP_CONVERSION', false ), you are essentially bypassing these checks.
Now we know that those checks didn’t work well with your specific environment. However, the reason for this is still unknown. The only way to find the answer is to gain access to an affected website and conduct further investigation. We attempted to collaborate with Namecheap but received a rather frustrating response. So now, we are exploring other ways.
Hello,
I have same issue from today before 3 hours.
I didn’t change/update/upload/install any plugins and there was nothing in error log file.
I am sending my server details as per below
Server architecture is Linux
Web server is Apache
PHP SAPI is litespeed
I have tested also
define( ‘WPO_USE_WEBP_CONVERSION’, false );
but steel not working.
Everything working perfectly good when WPO deactivated, but when once activate my admin and front-end both goes 503 error.
I have WPO 3.2.22
Hey,
Our hosting is with Godaddy and we are having the exact same issue. Once the plugin is activated our entire site goes down apart from the home page.
These are the details given to us by the hosting company:
PHP : 8.0
Web server type : Cpanel (shared hosting – which in their help states its linux)
Server architecture type : x86_64
The additional code bit provided as a solution in this thread didn’t work for us either.
Happy to duplicate our website to a staging one and give access if needed to run some tests
-
This reply was modified 11 months, 1 week ago by
RedRiteUK.
-
This reply was modified 11 months, 1 week ago by RedRiteUK.
@tes-india Also, please delete the .htaccess file from the ‘wp-content/uploads/’ directory. Additionally, ensure that you’ve added the following code inside the wp-config.php file: define( 'WPO_USE_WEBP_CONVERSION', false );
If it still doesn’t work, could you try changing the PHP version from cPanel? Sometimes, changing the PHP version can trigger a server restart, potentially resolving server-related issues.
@redriteuk You can also follow the same steps mentioned above.
In accordance with WordPress.org forum rules, I’m unable to request access here, and you can’t provide access in this forum. This would be a violation of the rules for both of us. For more information, please refer to: https://wordpress.org/support/guidelines/
I’m just waiting to receive access from our premium user through our official support channel. Once we have that, we intend to resolve this issue for good.
After deleting the wp-optimize folder in ‘plugin’ folder of WordPress manually, are there any other files that we should delete manually to get rid of all the remnants of this plugin?
Same issue here. Godaddy. 8.1 PHP version. Started with just Wp-Admin not working, then a few days later the whole site 503’d.
