The "Send emails" scheduled task failed with the "One or more errors occurred

Have you tried:  http://mysite.com/
http  (not https)
with the / at the end
restart the web site

When I use http rather than https, I do not see any errors in the error log BUT the scheduled tasks do not run at all as indicated by their time stamps.

Do you have / at the end?

Yes.  V4.30 actually appends a "/" if you omit it.

I find it interesting that the automated and manual methods for running the scheduled tasks posts to different URLs.  I'm looking at nopCommerce code right now to see if I can ascertain why.

We have got the same problem with 4.3 Version. The site doesn't send any email .

In the Log is written:
The "Send emails" scheduled task failed with the "One or more errors occurred. (The SSL connection could not be established, see inner exception.)" error (Task type: "Nop.Services.Messages.QueuedMessagesSendTask, Nop.Services".)

We can send the emails only when we push the buttom "run now" in the Schedule Task. Anyone fix this?

Thank you in advance
Bhisma Jena

Hi all,
same error on 4.3. Running manually it works (Send mail), automatically doesn't.
We have the / at the end of web site into Store configuration.

A lot of people with same error.. who can help us?
Thanks

Hi also our 4.3 nop site doesn't send any emails. Only manually . Anyone Knows how to fix this issue?

Lorenzo

Do we know if this is an identified bug or a configuration error?

The "Send emails" scheduled task failed with the "One or more errors occurred. (No such host is known.)"

We had the same problem with a nocpommerce 4.30 site hosted on linux. Http requests are being redirected to https with www, as are https without www redirected to https with www.
What fixed it was using https://www.example.com/ (example.com = site_domain) as the store url (Configuration -> Stores -> Store URL -> https://www.example.com/)

@Andrei Is this the case?

Most of our stores are hosted on subdomains https://store.example.com So this setup is not possible.

How can we resolve this?