Enhancement request: "Send report now" button

[zell-mbc]

I know this came up in the past already, but I'd like to ask for a "send email report now" feature again.

I am aware of the workaround to send a password reset email to test if the email setup is working in general, but I am dealing with a case where the weekly reports get stuck in my spam filter and troubleshooting means change a spam filter setting and wait a week to see if the change works.

[ruslandoga]

👋 @zell-mbc

Until this is implemented you can trigger a report manually with something like this:

$ cd plausible-ce
$ docker compose exec plausible bin/plausible remote

iex> domain = "dummy.site"
iex> site = Plausible.Repo.get_by!(Plausible.Site, domain: domain)
iex> Plausible.Workers.SendEmailReport.perform(%Oban.Job{args: %{"interval" => "weekly", "site_id" => site.id}})

[zell-mbc]

Sorry, took a while to get back to you.
I whitelisted the Plausible server on my email server and this morning the email reports came through, with SSL_ENABLED still on. All reports show zero traffic even though the Plausible website shows traffic but that's another issue I think.

As you suggested I went ahead just now and and removed the SMTP_HOSTS_SSL_ENABLED setting, restarted the docker-compose and tried the above plausible remote commands.

Still the same "Failed to send Email" error. So somehow the automated routine does something different than what I do manually.

[ruslandoga]

You might be running two Plausible instances :) Or at least it looks like that a bit: the report might come from the one that doesn't get events but has SMTP configured "correctly" somehow, and the other one might be getting events but has SMTP problems.

[ruslandoga]

Would you be able to show your SMTP-related configuration (the way Plausible sees it) and try sending a test email somewhere:

$ cd plausible-ce
$ docker compose exec plausible bin/plausible remote

iex> Application.get_env(:plausible, Plausible.Mailer)
#==> ... what does it return? ...

# pick one of your own mailboxes
iex> receiver = "[email protected]"
iex> email = Bamboo.Email.new_email(to: receiver, from: PlausibleWeb.Email.mailer_email_from(), text_body: "test")
iex> Plausible.Mailer.deliver_now(email)

[zell-mbc]

You might be running two Plausible instances :)

You got me worried for a moment, because I did indeed move things around before settling down on the current server and that DNS might point at a leftover instance isn't totally unrealistic, but no, did a quick docker compose down and both my docker exec shell I used to collect the information below, as well as the website which shows active traffic are gone. That would have been an embarrassing one :-)

Back to our subject:

When running the show mailer config command I noticed that SSL was still on, looks like a compose restart didn't do the trick. After a compose down / up I get ssl: [middlebox_comp_mode: false]and the email test works!

As well as manually sending a report, and this one even has got data in it?!
Left sent manually just now, right what was sent tonight

I'll think about this some more and will check the logs, but the "send-report-now" case is solved! Thanks for helping along…

[ruslandoga]

but no, did a quick docker compose down and both my docker exec shell I used to collect the information below, as well as the website which shows active traffic are gone

That would be the second, active instance in my example.