Status of the scheduler WP Cron ; Invalid date

THe plugin is not sending anymore the newsletter ; In the Mailpoet/Help screen : État du planificateur d’actions/WP CronVersion 3.9.3 Type de stockage DBStore Prochain déclenchement lancé Invalid date Dernier déclenchement lancé Invalid date Dernière exécution du worker lancée Invalid date it seems the date is invalid ; an issue in the DB ? Which informations could be helpfull to understand this issue ? name: ** email: ** PHP version: 8.2.27 MailPoet Free version: 5.23.2 MailPoet Premium version: 5.23.0 MailPoet Premium/MSS key: 54c618029dcf0f96** WordPress version: 6.9.4 Database version: 10.6.21-MariaDB Web server: Apache Server OS: Linux node199-eu.n0c.com 4.18.0-553.40.1.lve.el8.x86_64 #1 SMP Wed Feb 12 18:54:57 UTC 2025 x86_64 WP info: WP_MEMORY_LIMIT: 40M - WP_MAX_MEMORY_LIMIT: 512M - WP_DEBUG: - WordPress language: fr_FR - WordPress timezone: Europe/Paris PHP info: PHP max_execution_time: 360 - PHP memory_limit: 512M - PHP upload_max_filesize: 128M - PHP post_max_size: 128M Multisite environment?: No Current Theme: Amphibious (version 1.0.1) Active Plugin names: akismet/akismet.php, **, mailpoet-premium/mailpoet-premium.php, mailpoet/mailpoet.php, ** Sending Method: MailPoet MailPoet Sending Service: Is reachable: Yes - Ping response: 200 HTTP status code - API key state: valid - Premium key state: valid Sending Frequency: Géré par le service d’envoi MailPoet MailPoet sending info: Send all site's emails with: current sending method - Task Scheduler method: WordPress - Default FROM address: root@asmtplongee.org - Default Reply-To address: ** - Bounce Email Address: MailPoet Cron / Action Scheduler: Status: inactive - Is reachable: Yes - Ping URL: https://asmtplongee.org?mailpoet_router&endpoint=cron_daemon&action=ping - Ping response: pong - Last run start: 2026-05-11 11:22:28 - Last run end: 2026-05-11 11:22:28 - Last seen error: None Total number of subscribers: 173 Plugin installed at: 2020-12-18 14:49:04 Installed via WooCommerce onboarding wizard: false Sending queue status: Status: Unknown - Started at: 2026-04-16 14:48:59 - Emails sent: 0 - Retry attempts: 0 - Last seen error: None Data inconsistency status: Orphaned sending tasks: 0 - Orphaned sending task subscribers: 0 - Sending queue without newsletter: 0 - Orphaned subscriptions: 0 - Orphaned links: 0 - Orphaned newsletter posts: 0 When looking at the wp_mailpoet_log table, I found several similar error messages ; name mss level 400 message created_at “[2026-05-01T00:01:23.403486+00:00] raw_message mss.ERROR: requests-curl.failed context {“”curl_errno””:28,””curl_error””:””Connection timed out after 10001 milliseconds””,””curl_info””:{“”url””:”” https://bridge.mailpoet.com/api/v0/messages”” ;,””content_type””:null,””http_code””:0,””header_size””:0,””request_size””:0,””filetime””:-1,””ssl_verify_result””:0,””redirect_count””:0,””total_time””:10.001502,””namelookup_time””:0.000462,””connect_time””:0.0,””pretransfer_time””:0.0,””size_upload””:0.0,””size_download””:0.0,””speed_download””:0.0,””speed_upload””:0.0,””download_content_length””:-1.0,””upload_content_length””:-1.0,””starttransfer_time””:0.0,””redirect_time””:0.0,””redirect_url””:””””,””primary_ip””:””””,””certinfo””:[],””primary_port””:-1,””local_ip””:””””,””local_port””:-1,””http_version””:0,””protocol””:2,””ssl_verifyresult””:0,””scheme””:””https””,””appconnect_time_us””:0,””connect_time_us””:0,””namelookup_time_us””:462,””pretransfer_time_us””:0,””redirect_time_us””:0,””starttransfer_time_us””:0,””total_time_us””:10001502,””effective_method””:””POST””}} {“”free_plugin_version””:””5.23.2″”,””premium_plugin_version””:””5.23.0″”} This topic was modified 2 weeks, 3 days ago by alexandraka . This topic was modified 2 weeks, 3 days ago by alexandraka . Hi there, Thanks for sharing those logs — they’re very helpful! The “Invalid date” display in the System Status is actually a secondary symptom. The real issue is in your error logs: mss.ERROR: requests-curl.failed with curl_errno: 28 — “Connection timed out after 10001 milliseconds” This means your server is unable to reach the MailPoet Sending Service at bridge.mailpoet.com — the connection times out before it can even be established. That’s why your sending queue isn’t processing emails. This is a server-level networking issue, not a MailPoet bug. Here’s what I’d recommend: Step 1: Try the cURL Options plugin Install the Wise Builds cURL Options plugin , which lets you increase the timeout limit for cURL connections. Once installed, go to Settings > cURL Options , click “Add Rule” twice, and create two rules: Host Protocol Option Value your website URL https CURLOPT_TIMEOUT 30 bridge.mailpoet.com https CURLOPT_TIMEOUT 30 After saving, check if sending resumes. Step 2: Contact your hosting provider If the plugin above doesn’t help, please reach out to your hosting company and ask them to: Run curl https://bridge.mailpoet.com from your server’s command line to verify the connection works Check if any firewall, security module (e.g., mod_security), or network restriction is blocking outbound HTTPS connections to bridge.mailpoet.com Confirm there are no DNS resolution issues for that domain Ensure the server’s cURL library and PHP version are up to date You can share this message with them: “cURL requests from my website to https://bridge.mailpoet.com are timing out (cURL error 28, connect_time is 0.0, no IP resolved). Could you please check if there’s a firewall rule, security module, or network restriction blocking outbound HTTPS connections to that domain? Could you also verify DNS resolution for bridge.mailpoet.com from the server?” Step 3: Check for plugin conflicts If you have any security plugins active (such as WordFence, Sucuri, iThemes Security, or Ninja Firewall), try temporarily deactivating them and testing again. These can sometimes block outgoing connections. You can follow this guide to run a conflict test . About the “Invalid date” display: Once the connection issue is resolved and your cron tasks start completing successfully, the System Status timestamps should update to valid dates automatically. If they don’t, let us know and we can help with that as a follow-up. For more details, you can also check out our full troubleshooting guide: Sending Does Not Work (Troubleshooting) . Let us know how it goes! thank you for your support, I installed and activated the plugin and retried with the settings as described in https://kb.mailpoet.com/article/311-curl-issue-28-timeout Current PHP version: 8.2.27 Your server’s PHP cURL version information and features: cURL version:8.11.0 Host:x86_64-redhat-linux-gnu IPv6 support:yes Kerberos V4 support:no SSL support:yes SSL version:OpenSSL/1.1.1w libz HTTP deflate support:yes libz version:1.2.11 Protocols:dict, file, ftp, ftps, gopher, gophers, http, https, imap, imaps, ldap, ldaps, mqtt, pop3, pop3s, rtsp, scp, sftp, smb, smbs, smtp, smtps, telnet, tftp, ws, wss but… it does not works Sending Frequency: Géré par le service d’envoi MailPoet MailPoet sending info: Send all site’s emails with: current sending method – Task Scheduler method: WordPress – Default FROM address: root@asmtplongee.org – Default Reply-To address: root@asmtplongee.org – Bounce Email Address: MailPoet Cron / Action Scheduler: Status: inactive – Is reachable: Yes – Ping URL: https://asmtplongee.org?mailpoet_router&endpoint=cron_daemon&action=ping – Ping response: pong – Last run start: 2026-05-17 16:40:04 – Last run end: 2026-05-17 16:40:04 – Last seen error: None Total number of subscribers: 173 Plugin installed at: 2020-12-18 14:49:04 Installed via WooCommerce onboarding wizard: false Sending queue status: Status: Unknown – Started at: 2026-05-17 16:28:36 – Emails sent: 0 – Retry attempts: 0 – Last seen error: None Data inconsistency status: Orphaned sending tasks: 0 – Orphaned sending task subscribers: 0 – Sending queue without newsletter: 0 – Orphaned subscriptions: 0 – Orphaned links: 0 – Orphaned newsletter posts: 0 This reply was modified 1 week, 4 days ago by alexandraka . This reply was modified 1 week, 4 days ago by alexandraka . This reply was modified 1 week, 4 days ago by alexandraka . my host administrator is requesting more information about the curl request. It might be blocked by the WAF. So I would need more info about it (format, IP, any other usefull info).