PlotHost Posted January 24, 2019 Share Posted January 24, 2019 Hello, I see the daily cron job stops at "Automated Task: Starting SSL Sync". Any idea? Thanks. 0 Quote Link to comment Share on other sites More sharing options...
Revolution Posted January 25, 2019 Share Posted January 25, 2019 We noticed the exact same behavior 0 Quote Link to comment Share on other sites More sharing options...
vinc1402 Posted January 28, 2019 Share Posted January 28, 2019 It's also in the cron job email report. SSL Sync 523 Synced I have no idea what this is. I have active SSL certs for clients but not by WHMCS marketplace, they are just billed each cycle. So this is unclear for me. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted January 28, 2019 WHMCS Support Manager Share Posted January 28, 2019 Hi all, This is related to the new SSL Monitoring feature in 7.7: https://docs.whmcs.com/SSL_Monitoring If the task is not completing daily, please start your troubleshooting with these guides: https://help.whmcs.com/m/automation/l/678272-troubleshooting-the-cron-not-completing https://help.whmcs.com/m/automation/l/683269-advanced-cron-troubleshooting 0 Quote Link to comment Share on other sites More sharing options...
jackshreeve Posted March 7, 2020 Share Posted March 7, 2020 I'm experiencing exactly the same problem. The daily cron job stops at "Automated Task: Starting SSL Sync". If forced to run manually via SSH it completes successfully but not during the automatic daily run at 9am. I don't even get a cron report email. 0 Quote Link to comment Share on other sites More sharing options...
jackshreeve Posted March 8, 2020 Share Posted March 8, 2020 I managed to fix this by setting the permissions of cron.php to 755 I also made sure that the cron command was using the correct version of PHP /opt/cpanel/ea-php73/root/usr/bin/php -q /home/PATH/TO/crons/cron.php all -F n the above example, replace “ea-php99” with the PHP version assigned to the domain you wish to use. Look in the MultiPHP Manager for the actual PHP version assigned to a domain. 0 Quote Link to comment Share on other sites More sharing options...
jackshreeve Posted March 9, 2020 Share Posted March 9, 2020 23 hours ago, jackshreeve said: I managed to fix this by setting the permissions of cron.php to 755 I also made sure that the cron command was using the correct version of PHP /opt/cpanel/ea-php73/root/usr/bin/php -q /home/PATH/TO/crons/cron.php all -F n the above example, replace “ea-php99” with the PHP version assigned to the domain you wish to use. Look in the MultiPHP Manager for the actual PHP version assigned to a domain. Actually I've found out the cron command should not have the -F command. Otherwise this fix worked for me. e.g. /opt/cpanel/ea-php73/root/usr/bin/php -q /home/PATH/TO/crons/cron.php all 0 Quote Link to comment Share on other sites More sharing options...
baymax Posted March 12, 2020 Share Posted March 12, 2020 I receive the daily report which shows SSL is synced however when I go to the SSL Monitoring page, it hasn't updated the expiry dates for all the SSL. Some of the last update dates show over a month ago. And when I click the Revalidate SSL Status button, it refreshes the SSL dates but not for all of them. Refreshing the page reverts it back to old dates. 0 Quote Link to comment Share on other sites More sharing options...
Mark Posted February 14 Share Posted February 14 @baymax did you ever manage to resolve this issue? We are currently running "cron.php do --SslSync -vvv --email-report=1" in a loop to sync all SSL statuses but are only seeing expired expiry dates, while random checks on the actual websites using "curl -I" from the same server tells us that the expiry date is in the future. SELECT updated_at,expiry_date FROM tblsslstatus ORDER BY expiry_date; | 2021-11-23 14:41:43 | 2022-08-05 23:59:59 | | 2024-02-14 13:52:25 | 2022-08-11 23:59:59 | | 2023-07-24 08:25:45 | 2022-08-11 23:59:59 | | 2023-07-24 08:25:01 | 2022-08-11 23:59:59 | | 2022-03-02 09:20:58 | 2022-08-17 23:59:59 | | 2024-02-14 14:06:10 | 2022-09-15 23:59:59 | and curl -I --max-time 10 -v https://$DOMAIN | grep "expire date" * expire date: Apr 28 19:16:47 2024 GMT 0 Quote Link to comment Share on other sites More sharing options...
Mark Posted February 14 Share Posted February 14 54 minutes ago, Mark said: @baymax did you ever manage to resolve this issue? We are currently running "cron.php do --SslSync -vvv --email-report=1" in a loop to sync all SSL statuses but are only seeing expired expiry dates, while random checks on the actual websites using "curl -I" from the same server tells us that the expiry date is in the future. SELECT updated_at,expiry_date FROM tblsslstatus ORDER BY expiry_date; | 2021-11-23 14:41:43 | 2022-08-05 23:59:59 | | 2024-02-14 13:52:25 | 2022-08-11 23:59:59 | | 2023-07-24 08:25:45 | 2022-08-11 23:59:59 | | 2023-07-24 08:25:01 | 2022-08-11 23:59:59 | | 2022-03-02 09:20:58 | 2022-08-17 23:59:59 | | 2024-02-14 14:06:10 | 2022-09-15 23:59:59 | and curl -I --max-time 10 -v https://$DOMAIN | grep "expire date" * expire date: Apr 28 19:16:47 2024 GMT We figured it out. It's an issue with curl 7.29.0 on CentOS 7.9. You need at least curl 7.34.0 to be able to use CURLOPT_CERTINFO which is used in the getCertificate($domain) function which is used when SslSync is called. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.