Error

Hello,

Sorry to hear about your unfortunate event. The plugin is designed to avoid crashing a website. If you have other plugins actively controlling your heartbeat it may cause issues where it won’t activate. I would be happy to assist you if you provide more information about your website such as:

1. What is your hosting environment?
2. Your WordPress and PHP version.
3. Active plugins list.
4. Can you post your error log so we can pinpoint the root of this issue?

Looking forward to hearing back from you!

• This reply was modified 1 year ago by Steven Stern (sterndata).
• This reply was modified 1 year ago by Codeloghin.
• This reply was modified 1 year ago by Yui.

@tominthephilippines

Did you install this in a local machine or is the WordPress version 6.4.0?

@codeloghin

Thanks for your reply. Here is some information regarding your questions:

1. I am on Cloudways DO
2. WP version 6.4.1 and PHP version 8.1
3. Active Plugins (33)
   • Advanced Dynamic Pricing for WooCommerce: by AlgolPlus – 4.5.3
   • Astra Pro: by Brainstorm Force – 4.5.1
   • Autoptimize: by Frank Goossens (futtta) – 3.1.10
   • CMP – Coming Soon & Maintenance Plugin: by NiteoThemes – 4.1.10
   • Complianz | GDPR/CCPA Cookie Consent: by Really Simple Plugins – 6.5.5
   • Crocoblock Wizard: by Crocoblock – 1.2.8
   • Disable Cart Fragments: by Optimocha – 2.3
   • Yoast Duplicate Post: by Enrico Battocchi and Team Yoast – 4.5
   • Elementor Pro: by Elementor.com – 3.17.1
   • Elementor: by Elementor.com – 3.17.3
   • HT Script Pro: by CodeCarnival – 1.1.0
   • JetBlocks For Elementor: by Crocoblock – 1.3.8.2
   • JetBlog For Elementor: by Crocoblock – 2.3.5.1
   • JetElements For Elementor: by Crocoblock – 2.6.14
   • JetMenu: by Crocoblock – 2.4.2
   • JetTricks: by Crocoblock – 1.4.7
   • JetWooBuilder For Elementor: by Crocoblock – 2.1.8
   • Printful Integration for WooCommerce: by Printful – 2.2.6
   • Product Import Export for WooCommerce: by WebToffee – 2.3.7
   • Rank Math SEO: by Rank Math – 1.0.206
   • SVG Support: by Benbodhi – 2.5.5
   • TrackShip for WooCommerce: by TrackShip – 1.7.1
   • Variation Swatches for WooCommerce: by CartFlows – 1.0.7
   • Advanced Shipment Tracking for WooCommerce: by zorem – 3.6.2
   • WooCommerce Cart Abandonment Recovery: by CartFlows Inc – 1.2.25
   • WooCommerce PayPal Payments: by WooCommerce – 2.4.1
   • WooCommerce: by Automattic – 8.3.1
   • ShopLentor Pro – WooCommerce Builder for Elementor & Gutenberg: by HasThemes – 2.2.8
   • ShopLentor – WooCommerce Builder for Elementor & Gutenberg: by HasThemes – 2.7.3
   • Wordfence Security: by Wordfence – 7.10.7
   • WP Fastest Cache: by Emre Vona – 1.2.2
   • WP Mail SMTP: by WP Mail SMTP – 3.10.0
   • WP-Optimize – Clean, Compress, Cache: by David Anderson
   • Ruhani Rabin
   • Team Updraft – 3.2.22
4. Error log:
   
   2023-11-27T00:56:57+00:00 CRITICAL Uncaught Error: Call to undefined function shell_exec() in /home/1128085.cloudwaysapps.com/zeswcxkdjx/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/heartbeat-controller.php:427
   
   Stack trace: 0 /home/1128085.cloudwaysapps.com/zeswcxkdjx/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/heartbeat-controller.php(438): dfehc_get_system_load_average() 1 /home/1128085.cloudwaysapps.com/zeswcxkdjx/public_html/wp-admin/includes/plugin.php(2318): include_once(‘/home/1128085.c…’) 2 /home/1128085.cloudwaysapps.com/zeswcxkdjx/public_html/wp-admin/includes/plugin.php(663): plugin_sandbox_scrape() 3 /home/1128085.cloudwaysapps.com/zeswcxkdjx/public_html/wp-admin/plugins.php(58): activate_plugin() 4 {main}
   
   thrown in /home/1128085.cloudwaysapps.com/zeswcxkdjx/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/heartbeat-controller.php on line 427

I am running the Heartbeat Control by WP Rocket plugin now, without issues. But I’d also like to know the advantages of your plugin over the WP Rocket one.

Cheers and thanks!
Tom

@zedred45

Not running on a local machine and running WP version 6.4.1

Cheers,
Tom

Dear Tom @tominthephilippines

Thank you for your comprehensive reply. To answer your question, compared to Heartbeat Control by WP Rocket this plugin automatically decides the optimal interval based on a few factors in your hosting environment (such as server load, response time, visitors, etc.) To achieve this it needs to fetch this data with minimal impact on existing resources. It has a few fallbacks for situations where some hosts might not have this data readily available or as in your case where the hosting might block these requests. It seems that Cloudways has further tightened some of their restrictions on getting the server load most probably to maintain their hosting environment as safe as possible. Even if the plugin will move on to calculate these variables if blocked, it seems that Cloudways didn’t allow the plugin to move on in this instance.

I have just launched a new version(1.2.7) that is compatible with these blocks placed by hosts like Cloudways. I would like to thank you for reporting this problem and have added credits to you in the release notes section:
https://www.ads-software.com/plugins/dynamic-front-end-heartbeat-control/#developers

The advantage of this plugin is for websites where a manual interval is not the best-case scenario such as websites that experience high fluctuations in traffic where owners/developers will have to constantly update the interval depending on the current flow of traffic to achieve a smooth experience for their visitors. Or just for people who have no knowledge of setting a heartbeat interval for their website.

In the upcoming releases, new features will be added such as optimizing your website’s database and a few additional tweaks to allow users to further maximize their website’s performance.

Hope that you will enjoy this new release and find this plugin of use.

For any other questions feel free to reach out.

Best regards,
Codeloghin

Hi there Codeloghin,

Happy that I could provide some help in this matter, and thank you very much for the credits as wel as your comprehensive explanation of how the plugin works and compares to the other one. Cloudways helpdesk told me to just set everything to 200… which already seemed a bit weird to me as a ‘set and forget’ setting.

I have replaced it with your plugin, which seems to work fine now and doing its job.

Thanks again and I’m looking forward to future updates!

Cheers,
Tom

Hi Tom?@tominthephilippines,

I am happy to hear that the plugin works for you now.

May I know the website you are using this on and if you are looking to alleviate any specific performance issues?

If you prefer to keep some of this data private, feel free to reach out to me by going to the plugin page and clicking on my name. It will take you to my Fiverr profile where you can send me a message. I am interested in seeing various use cases for this plugin as in turn it will help me with launching new features that will help users. I could also maybe pinpoint any issues that could be easy to fix as I also offer WordPress performance enhancing services

Looking forward to your feedback.

Best regards.

Codeloghin

Hi there Codeloghin,

My intention for using your plugin was to get the server load down, especially the CPU usage which constantly spiked to 100%. Cloudways hasn’t been my best experience, even after scaling up to DO4 I was having the same issue, not even to mention that the server can’t handle more than 30-35 concurrent users, which is ridiculous if you look at their pricing. I have cheap hosting that can handle more concurrent users.

So I moved that site back to my shared hosting, which loads slower I admit, but at least users don’t get to see a database error because the server can’t handle simple tasks. The website is https://www.carcoholic.com.

I did notice another error in my logs this morning, so it would be great if you could have a look at this:

2023-11-30T02:28:13+00:00 CRITICAL Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, function “dfehc_track_and_expire_user_activity” not found or invalid function name in /home/carcoholic/domains/carcoholic.com/public_html/wp-includes/class-wp-hook.php:326 Stack trace: #0 /home/carcoholic/domains/carcoholic.com/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() #1 /home/carcoholic/domains/carcoholic.com/public_html/wp-admin/includes/ajax-actions.php(3494): apply_filters() #2 /home/carcoholic/domains/carcoholic.com/public_html/wp-includes/class-wp-hook.php(324): wp_ajax_heartbeat() #3 /home/carcoholic/domains/carcoholic.com/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #4 /home/carcoholic/domains/carcoholic.com/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #5 /home/carcoholic/domains/carcoholic.com/public_html/wp-admin/admin-ajax.php(188): do_action() #6 {main} thrown in /home/carcoholic/domains/carcoholic.com/public_html/wp-includes/class-wp-hook.php on line 326

Cheers,
Tom

Dear Tom @tominthephilippines,

Please open a support ticket by going to the plugin page and clicking on my name. I would love to have a closer look at this.

Looking forward to hearing back from you.

Best regards,

Codeloghin

Hi Tom?@tominthephilippines,

A new version has just been released that also has database cleaning and optimization included(1.2.8). It’s always recommended you back up your website before using these functions. When you are available, feel free to reach out to me about your previous website issue. I would be happy to assist you as it seems you might have a corrupted database and/or core files. This might cause your website to use more server resources than needed.

Best regards,

Codeloghin

Hi @Codeloghin,

My apologies for the late reply, unfortunately I got sick and then a bunch of work piled up. The update to version 1.2.8 was already performed and I just checked my logs, and there it seems to show the latest critical error on the 4th of December and nothing after that anymore. So the issue seems to be fixed, at least for now, but I’ll keep checking every now and then.

I do have another question: When I check the DFEHC settings, I noticed the Redis settings were not correct, so I changed the IP and port to the correct one. I just don’t know what the Redis Unix Socket is and if that needs to be changed, and if so, where I could possibly find this?

Thanks again!

Cheers,
Tom

Hi Tom?@tominthephilippines,

No worries, happy to hear the website is getting back on track. You can always open a message support request on my Fiverr profile for further help. Maybe the error was around the time of the transfer, between other plugin updates, or an expired certificate. Multiple reasons may cause this.

Regarding the Redis settings, the plugin will automatically detect your server configuration. In the event it can’t do that, it will create a notification that you can also find in your error log and that’s when setting it yourself from the settings page will help. It will ignore other settings if it already found a connection. That area won’t cause issues for users even if they set a wrong value or if the hosting environment doesn’t have Redis, the plugin will make use of the WordPress built-in caching method. Hosting environments either have one option or the other. There is no need to set the UNIX socket if your hosting doesn’t have it. Your hosting will be able to provide you with their exact Redis method and connection values if you need these for various uses. With the launch of the plugin website soon, the settings page will also be updated to provide a bit more data on your hosting environment. Currently, the main focus has been maximizing the heartbeat efficiency.

If you think you have managed this on your own then I’m happy that the outcome was good and would appreciate it if you could revisit your initial review of the plugin.

You can always reach out if you have other questions or concerns.

Best regards,

Codeloghin

Hi Tom @tominthephilippines,

No worries, happy to hear the website is getting back on track. You can always open a message support request on my Fiverr profile for further help. Maybe the error was around the time of the transfer, between other plugin updates, or an expired certificate. Multiple reasons may cause this.

Regarding the Redis settings, the plugin will automatically detect your server configuration. In the event it can’t do that, it will create a notification that you can also find in your error log and that’s when setting it yourself from the settings page will help. It will ignore other settings if it already found a connection. That area won’t cause issues for users even if they set a wrong value or if the hosting environment doesn’t have Redis, the plugin will make use of the WordPress built-in caching method. Hosting environments either have one option or the other. There is no need to set the UNIX socket if your hosting doesn’t have it. Your hosting will be able to provide you with their exact Redis method and connection values if you need these for various uses. With the launch of the plugin website soon, the settings page will also be updated to provide a bit more data on your hosting environment. Currently, the main focus has been maximizing the heartbeat efficiency.

If you think you have managed this on your own then I’m happy that the outcome was good and would appreciate it if you could revisit your initial review of the plugin.

You can always reach out if you have other questions or concerns.

Best regards,

Codeloghin