Scheduler: Error Missing parameter : displayFormat for task

dev · March 21, 2022, 2:29pm

After updating from V3 to V4, we are seeing the error:
Scheduler: Error Missing parameter : displayFormat for task


/usr/share/nginx/html/matomo/plugins/ScheduledReports/API.php(724): Warning - Invalid argument supplied for foreach() - Matomo 4.8.0 - Please report this message in the Matomo forums: https://forum.matomo.org (please do a search first as it might have been reported already)

Any easy way to update all the reports so they’re not throwing errors?

MisterGenest · March 23, 2022, 8:10pm

This sometimes occurs when going from Matomo 3 to Matomo 4 because Matomo 4 uses PhpMailer instead of Zend Mail.

One workaround is the following:
Try to send a test email from the Matomo application itself. If there are any errors, the output from the Console command should provide us with additional information to resolve the issue. The command to run would be as follows:

./console core:test-email abcdefg@example.com where the email is your email.

There is a known issue with the default PHPMailer settings that prevents Matomo from sending emails through a Mail server that uses a Self-Signed certificate. If this is the cause of the issue, then you can follow the steps in this GitHub issue to the vendor/phpmailer/phpmailer/src/PHPMailer.php file:

github.com/matomo-org/matomo

Unable to send mails through SMTP server with self-signed cert (and undescriptive error msg)

opened 01:36PM - 03 Jan 22 UTC

tgoeg

Potential Bug

## Expected Behavior Using password reset or ./console core:test-emails sho…uld send out mails. ## Current Behavior I get errors when trying both, but no error messages that hint at the actual problem: ``` $ ./console core:test-email user@example.org 2022-01-03 13:18:42 SERVER -> CLIENT: 220 mysmtp.example.org Microsoft ESMTP MAIL Service ready at Mon, 3 Jan 2022 14:18:41 +0100 2022-01-03 13:18:42 CLIENT -> SERVER: EHLO localhost.localdomain 2022-01-03 13:18:42 SERVER -> CLIENT: 250-mysmtp.example.org Hello [10.0.0.1] 250-SIZE 37748736 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-8BITMIME 250-BINARYMIME 250 CHUNKING 2022-01-03 13:18:42 CLIENT -> SERVER: STARTTLS 2022-01-03 13:18:42 SERVER -> CLIENT: 220 2.0.0 SMTP server ready 2022-01-03 13:18:42 SMTP Error: Could not connect to SMTP host. 2022-01-03 13:18:42 CLIENT -> SERVER: QUIT 2022-01-03 13:18:42 SERVER -> CLIENT: 2022-01-03 13:18:42 SMTP ERROR: QUIT command failed: 2022-01-03 13:18:42 SMTP Error: Could not connect to SMTP host. ERROR [2022-01-03 13:18:42] 3635150 Uncaught exception: /var/www/matomo.example.org/vendor/phpmailer/phpmailer/src/PHPMailer.php(2153): SMTP Error: Could not connect to SMTP host. [Query: , CLI mode: 1] [PHPMailer\PHPMailer\Exception] SMTP Error: Could not connect to SMTP host. core:test-email emailAddress ``` ## Possible Solution My SMTP server has a self-signed certificate. I'm trying to get people to fix that as well (as this would be the better solution), but wanted to report the problem here anyway. Another option would be adding the CA's certificate to the matomo host so its self-signed certificates could be trusted. What makes it work as well is changing vendor/phpmailer/phpmailer/src/PHPMailer.php ``` 331 /** 332 * Options array passed to stream_context_create when connecting via SMTP. 333 * 334 * @var array 335 */ 336 // public $SMTPOptions = []; 337 public $SMTPOptions = [ 338 'ssl' => [ 339 'verify_peer' => false, 340 'verify_peer_name' => false, 341 'allow_self_signed' => true, 342 ] 343 ]; ``` However, that's a bad location to fix this issue. My suggestion would be to - improve the error message (however, setting `public $SMTPDebug = 0;` to `4` did not improve it..); I am not a developer, maybe PHPMailer can offer better debugging info and I just do not know how to improve it. Probably at least add a hint in the error messages? `echo QUIT | openssl s_client -starttls smtp -crlf -connect mysmtp.example.org:25` quickly showed the error for example - provide a config option to allow self-signed certificates ## Steps to Reproduce (for Bugs) 1. Setup mail server with self-signed certificate and STARTTLS capabilities 2. Configure matomo to use it 3. Use `./console core:test-email user@example.org` or perform a password reset to get the error. ## Context Resetting a user password is currently impossible in this context. ## Your Environment * Matomo Version: 4.6.2 * PHP Version: 7.4 * Server Operating System: Ubuntu 18.04 * Additionally installed plugins: irrelevant

Please note that you will need to apply these changes to the file in the phpmailer folder each time you perform an update to Matomo.

dev · March 23, 2022, 9:19pm

Thanks for the info! I tested sending an email from the console and it went through without any issue. Any other ideas about what it could be or could it still be related to the mailer even though the test went through?

I confirmed if I go to generate a new report, it does in fact get delivered. It appears their is a configuration change from previous Matomo versions that is causing the older reports to fail. Scheduler: Error Missing parameter : displayFormat for task. Can this field be updated through a SQL command?