Kowsar Hossain

Based on the collective data I’ve gathered so far, I’ve compiled the following key points:

1. There have been several reports of this issue, all occurring within the same timeframe.
2. Notably, all these reports are originating from Namecheap users, and it’s worth noting that Namecheap utilizes the LiteSpeed server internally.
3. I conducted a test of our plugin on another hosting platform that also uses LiteSpeed servers, and it functioned perfectly there. This suggests that the issue might not be related to the LiteSpeed server itself.
4. Our plugin hasn’t undergone any recent updates; the last one was months ago. So, recent changes in the plugin’s codebase can be ruled out as a potential cause.
5. There’s one report indicating that CPU usage spikes to 100% during the error occurrence. In my experience, certain shared hosting providers impose Disk I/O limits on their users. Consequently, when a process involving a high volume of file read/write operations (such as cache preloading) is initiated, the CPU can quickly hit its limit due to these restrictions. I didn’t expect Namecheap to be one of these providers.

Considering this information, I have reason to suspect that the issue might be originating from Namecheap, possibly due to alterations in their server configuration or additional resource usage restrictions imposed on their shared hosting users – I don’t know. While I can’t confirm whether all Namecheap users are affected, it is evident that all users reporting this issue are using Namecheap.

I am interested in hearing what Namecheap hosting has to say about this matter, perhaps you guys can reach out to their support? If the root cause lies within Namecheap, I hope they will address it promptly. On the other hand, if Namecheap believes the issue is related to WP-Optimize (despite the fact that millions of users use WP-Optimize without any issues), I believe they could provide more specific information about this, such as which part of WP-Optimize’s codebase is triggering the issue. As a hosting provider, they should be well-equipped to provide such information.

@wp-opti What happens when you manually click on the “Preload” button? Once the preload process finishes, can you confirm whether all pages have been cached or not? Thanks

@jmsstuff I believe it’s simply a conflict with the ‘Local Google Fonts‘ plugin. If you add fonts manually, it should work. If not, please let us know, and we will initiate a separate investigation. Thanks.

Thanks for providing additional information. Since I’ve already included this investigation in the queue, I’ll mark this thread as resolved for the time being. If we require further information, I’ll make another post here.

@jmsstuff
You’re right; it appears that the “Local Google Fonts” plugin isn’t compatible with WP-Optimize, particularly with the CSS Minification feature. In my view, adding compatibility for this plugin seems like a valuable addition, so I will consult with my teammates to explore the potential of incorporating compatibility with this plugin in the future. However, until such compatibility is implemented, I’m afraid you’ll need to disable the CSS Minification feature to get the plugin to work. Thank you.

@wp-opti
Right, if you don’t see “Cached by WP-Optimize…” at the bottom, it indicates that you are viewing an uncached page. Ideally, all pages should be preloaded simultaneously if the scheduled preloader is enabled.

1. Could you clarify what you actually mean by “preload turned on every 10 hours“? Are you saying that your website’s cache lifespan is set to 10 hours, and the preload schedule is configured to “same as cache lifespan“? Please confirm.
2. Could you provide a link to an example page that isn’t being preloaded? This will allow me to check whether that page is included in your sitemap, as the preloader only works for pages listed in the sitemap.

Thanks

@stathious @mhoerner @dotch @amsgator Are you guys, by any chance, using Namecheap hosting? Additionally, are you using the “LiteSpeed Cache” plugin in conjunction with WP-Optimize? Just trying to connect a few dots, this information will help. Thanks

@stathious @mhoerner @dotch Can you also confirm which server you’re using, specifically whether it’s a LiteSpeed server or not?

@subodhkaushik13 Since you’re mentioning WPML, the WP-Optimize premium version should support it. However, if it doesn’t, as a premium user, you can reach out to us through our premium support channel. Please note that according to www.ads-software.com forum rules, we are unable to provide support for the premium version here.

Note: I’ll discuss with my teammates about the possibility of adding CURCY support into WP-Optimize.

@2022dmi You can set the file permission to 644. For more details, please check this article: https://www.malcare.com/blog/wordpress-file-permissions/

Error log should be available in cPanel or the hosting dashboard, or you can ask your hosting provider about it.

Hi @subodhkaushik13,

This is Kowsar from the development team.

Currently, the CURCY Multi-Currency feature isn’t compatible with WP-Optimize. While the CURCY team has extended support to several caching plugins, WP-Optimize is not included in that list. You may also consider reaching out to them to inquire about the possibility of adding support for WP-Optimize in the future.

I’ve replied about this in another topic you’ve created; let’s continue there.

@2022dmi You may ask your hosting provider about this issue.

I’m assuming “wp-content/advanced-cache.php” file is not writable in your case. You can ask your hosting provider to configure the appropriate writing permission for this file. Any caching plugin you use will require the ability to write to this file to function properly.

Thanks @pfefferle, this’ll help a lot.

@xizor, we’ve taken a note of this issue and will investigate based on the information we have so far. If we need more information, we’ll let you know. Thanks for reporting this issue.