Empty table while server trigger tasks using iterate

Hello,

I've done a process to fetch emails from an adress, and save/process the files attached.
I use multiple iterate, because I need to fetch emails from several configurable addresses, and send an email to other configurable addresses.
It works great when run from Easy Morph desktop.
But when I trigger the tasks from Easy Morph server, it fails.

I've put some verifications to avoid the fail and to see what's happening.
As I can see, tasks is not waiting for the iterate result, it return an empty table.
I have multiple iterate, the first return empty results.

What I do :
I add email addresses and subjects from an other table, and then iterate on a module.
This module take in parameter the addresses and subjects I added before, and fetch emails, save attachment.
It create some columns bases on emails information, because I need to setup an archive folder and specific path depending on the attachment, and that's all.
I've added a "skip action on condition" just after, where "skip the rest of actions if table is empty".
When I use Easy Morph desktop, all my process is functionnal, I receive a confirmation email.
When I trigger the task from Easy Morph Server, it stop because the result of the iterate is empty...

Screens from Easy Morph Desktop where it is "working" :

And here the module where the first iteration is done :

Can someone tell me why I can't run this directly from a server tasks?

After trying multiples things to debug, I got this :

#An error occurred while attempting to establish an SSL or TLS connection.

This usually means that the SSL certificate presented by the server is not trusted by the system for one or more of the following reasons:

  1. The server is using a self-signed certificate which cannot be verified.
  2. The local system is missing a Root or Intermediate certificate needed to verify the server's certificate.
  3. A Certificate Authority CRL server for one or more of the certificates in the chain is temporarily unavailable.
  4. The certificate presented by the server is expired or invalid.

Another possibility is that you are trying to connect to a port which does not support SSL/TLS.

It is also possible that the set of SSL/TLS protocols supported by the client and server do not match.

See MailKit/FAQ.md at master · jstedfast/MailKit · GitHub for possible solutions.

So it's not an Easy Morph problem.
I don't know why it do this with the server and not with the desktop app.
I will see the problem with my network guys. Ty

2 Likes

Hi @WindBlast and welcome to the Community!

In one of the recent versions, we've added restrictions on the use of self-signed or invalid SSL certificates both in Desktop and Server, as a security measure.

However, you can still remove the restrictions in the application settings:

In EasyMorph Desktop, go to menu About, and click "Application preferences":

In EasyMorph Server, sign in as a Server administrator, and then go to the "Settings" tab:

Generally, we don't recommend permitting all self-signed or invalid SSL certificates. Instead, if necessary, whitelist only specific certificates - the security settings have this option.