Useful or not, from you.
wekan Bug: Password reset emails not sent


Other Wekan issues can be added here.

Server Setup Information:

  • Did you test in newest Wekan?: No
  • For new Wekan install, did you configure root-url correctly ? Yes
  • Wekan version: 1.74
  • If this is about old version of Wekan, what upgrade problem you have?:
  • Operating System: RHEL 7.5
  • Deployment Method(snap/docker/sandstorm/mongodb bundle/source): Docker Swarm
  • Http frontend if any (Caddy, Nginx, Apache, see config examples from Wekan GitHub wiki first): Nginx in Docker Swarm
  • Node Version: 8.12
  • MongoDB Version: 3.2.21
  • ROOT_URL environment variable http(s)://(subdomain) https://wekan.internal-url

Problem description: When our users use the password reset function in Wekan, emails are not sent to the SMTP server due to a connection timeout. However other emails through Wekan such as when actions are performed on a watched board are sent like normal. The error in the log is:

Exception while invoking method 'forgotPassword' Error: Connection timeout    |     at SMTPConnection._formatError (/build/programs/server/npm/node_modules/meteor/email/node_modules/node4mailer/lib/smtp-connection/index.js:558:19)    |     at SMTPConnection._onError (/build/programs/server/npm/node_modules/meteor/email/node_modules/node4mailer/lib/smtp-connection/index.js:531:20)    |     at Timeout._connectionTimeout.setTimeout (/build/programs/server/npm/node_modules/meteor/email/node_modules/node4mailer/lib/smtp-connection/index.js:249:18)    |     at ontimeout (timers.js:498:11)    |     at tryOnTimeout (timers.js:323:5)    |     at Timer.listOnTimeout (timers.js:290:5)

The configuration in the docker-compose.yaml file is:

      - MAIL_URL=smtp://

In the Wekan admin panel: image

The settings match but for some reason password resets fail. Can you tell me when the docker variables are used and when the admin panel variables are used for sending mail and if there is some different function for sending mail for password resets?

Out current workaround is to manually pull the password reset token out of the database but this isn't very sustainable for thousands of users.

That's a useful answer
Without any help

No it's a SMTP server/relay provided on our corporate network. Unfortunately I don't know the architecture. Just to be clear, emails are working from Wekan, but only during low-usage times (evenings, weekends etc.)