Send And Wait for Response not sending email

Questions
1

Hello, i’m using n8n in a hostinger site since a couple of weeks. Everything was working fine until today; i’ve tried to use a SendAndWaitForResponse email block (that worked fine ‘til now), but the flow hangs because email is not sent to the user who should approve.

Credentials are correct because if i use a normal email block, the message is sent.

Is anyone encountering a similar problem? I’ve updated n8n to 1.111.0 version and cannot find anything strange in the logs.

Thanks in advance for your help, greetings

Cris

2

Hello @cdiscla,

When you say the workflow “hangs” do you mean that it keeps waiting for a long time without sending the email, or does it fail?

Also, could you confirm that the recipient’s email address is correct?

3

Hello, thank you for your answer; the workflow keeps waiting for a long time, but the email never arrives. The recipient is correct, if i use the plain SendEmail block, it works.

4

So you’re using the Email node, right?

image
image185×206 4.91 KB

You also mentioned that it’s working, do you mean it works when you send the email to yourself?

So does it only work when you send the email to yourself, but fails when sending it to anyone else?

5

I use SendAndWait for Response. It never sends email to anyone; if i use SendEmail (without the approvals flow), it works. Seems that email are not delivered in case of SendAndWait.

I’ve tried to activate a n8n cloud account and the same flow works; seems to be an issue related to my domain in Docker, but don’t know how to check for further infos.

6

Oh, I understand now,
Are your webhook settings configured correctly?
I mean, are the webhooks working properly? If not, that’s probably the issue here.

7

Hi there @cdiscla can you paste the image of the logs by typing this in your terminal.. Cheers
docker logs --tail=200

8

My docker.compose.yml has:

environment:

  • N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
  • N8N_PORT=5678
  • N8N_PROTOCOL=https
  • NODE_ENV=production
  • WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
  • GENERIC_TIMEZONE=${GENERIC_TIMEZONE}

in .env $SUBDOMAIN and $DOMAIN_NAME are correctly configured.

I don’t know if i need other settings

9

i get a series of this warning:

ValidationError: The ‘X-Forwarded-For’ header is set but the Express ‘trust proxy’ setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See Page Redirection for more information.
at Object.xForwardedForHeader (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:187:13)
at Object.wrappedValidations. [as xForwardedForHeader] (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:398:22)
at Object.keyGenerator (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:671:20)
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:724:32
at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected]/node_modules/express-rate-limit/dist/index.cjs:704:5 {
code: ‘ERR_ERL_UNEXPECTED_X_FORWARDED_FOR’,
help: ‘https://express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/’
}
[license SDK] license successfully renewed

10

hmm, can you try remove this slash / at the end

Also, is the webhook node working in general working on your instance?

12

webhooks seem working; when i create a webchat it runs fine

13

Is your problem solved? Let us know then

14

not yet :frowning: email using Send And Wait for Response is not being sent

16

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.