starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Email Notification Not Working #3090

New issue

Closed

opened 2026-02-28 03:17:32 -05:00 by deekerman · 13 comments

deekerman commented

2026-02-28 03:17:32 -05:00

Owner

Originally created by @denispollini on GitHub (Feb 1, 2024).

⚠️ Please verify that this question has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

Can't send notication email.

📝 Error Message(s) or Log

Error: Connection timeout
    at SMTPConnection._formatError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:784:19)
    at SMTPConnection._onError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:770:20)
    at Timeout.<anonymous> (/app/node_modules/nodemailer/lib/smtp-connection/index.js:229:22)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7) {
  code: 'ETIMEDOUT',
  command: 'CONN'
}

🐻 Uptime-Kuma Version

Versione: 1.23.11

💻 Operating System and Arch

Debian GNU/Linux 10 x86_64

🌐 Browser

Brave

🖥️ Deployment Environment

Runtime: Docker version 23.0.2, build 569dd73
Database:
Filesystem used to store the database on:
number of monitors:

Originally created by @denispollini on GitHub (Feb 1, 2024). ### ⚠️ Please verify that this question has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem Can't send notication email. ### 📝 Error Message(s) or Log ```log Error: Connection timeout at SMTPConnection._formatError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:784:19) at SMTPConnection._onError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:770:20) at Timeout.<anonymous> (/app/node_modules/nodemailer/lib/smtp-connection/index.js:229:22) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) { code: 'ETIMEDOUT', command: 'CONN' } ``` ### 🐻 Uptime-Kuma Version Versione: 1.23.11 ### 💻 Operating System and Arch Debian GNU/Linux 10 x86_64 ### 🌐 Browser Brave ### 🖥️ Deployment Environment - Runtime: Docker version 23.0.2, build 569dd73 - Database: - Filesystem used to store the database on: - number of monitors:

deekerman

2026-02-28 03:17:32 -05:00

closed this issue
added the
Stale

A:notifications

help

cannot-reproduce
labels

deekerman commented

2026-02-28 03:17:37 -05:00

Author

Owner

@denispollini commented on GitHub (Feb 1, 2024):

The version of uptime kuma is random because i don't know how to check in docker container

@denispollini commented on GitHub (Feb 1, 2024): The version of uptime kuma is random because i don't know how to check in docker container

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@apio-sys commented on GitHub (Feb 1, 2024):

Probably some issue with your underlying mail system. It really depends on what you are using for sending out email. A local sendmail() or exim or postfix, an external SMTP mail relay controlled by yourself or external, etc. Without that info and some initial troubleshooting steps hard to answer or help I think.

@apio-sys commented on GitHub (Feb 1, 2024): Probably some issue with your underlying mail system. It really depends on what you are using for sending out email. A local sendmail() or exim or postfix, an external SMTP mail relay controlled by yourself or external, etc. Without that info and some initial troubleshooting steps hard to answer or help I think.

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 1, 2024):

Sorry, but we can't support version 1.10.0. Said release was made a while ago and digging into said code is not maintainable for us.

The version of uptime kuma is random because i don't know how to check in docker container

I don't quite get what you are trying to tell us here.
If you are asking for a guide on how to update, please check here: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Note

the deployed version is also visible here:

For your actual issue, please ensure that you are using the exact configuration as in your mail program and that said configuration works there.

These might be related (without additional context from your side, we are unable to tell more..):

#1713
#2793

@CommanderStorm commented on GitHub (Feb 1, 2024): Sorry, but we can't support version `1.10.0`. Said release was made a while ago and digging into said code is not maintainable for us. > The version of uptime kuma is random because i don't know how to check in docker container I don't quite get what you are trying to tell us here. If you are asking for a guide on how to update, please check here: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update > [!NOTE] > the deployed version is also visible here: > ![image](https://github.com/louislam/uptime-kuma/assets/26258709/0570eda0-f732-4845-abd9-72cbafa7a995) For your actual issue, please ensure that you are using the exact configuration as in your mail program and that said configuration works there. These might be related (without additional context from your side, we are unable to tell more..): - #1713 - #2793

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@denispollini commented on GitHub (Feb 1, 2024):

I checked my uptime kuma version and modified the 1st post

@denispollini commented on GitHub (Feb 1, 2024): I checked my uptime kuma version and modified the 1st post

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@denispollini commented on GitHub (Feb 1, 2024):

I use my mail server for send email.

This is my Uptime Kuma Configuration:

@denispollini commented on GitHub (Feb 1, 2024): I use my mail server for send email. This is my Uptime Kuma Configuration: ![image](https://github.com/louislam/uptime-kuma/assets/81813145/d47fd6d9-61a6-4d4a-8201-76d40b8195e2)

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@denispollini commented on GitHub (Feb 2, 2024):

hi any news about it?

@denispollini commented on GitHub (Feb 2, 2024): hi any news about it?

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 2, 2024):

I don't know any reason why your mail server is timeouting these requests, but not when you send them with the same credentials from your local machine.
I sort of suspect a networking issue or a copy and paste/differing configuration issue because sending mails works on my machine.

You can try if you can contact the mail server via https://github.com/louislam/uptime-kuma/wiki/Troubleshooting or look into your mailservers logs

@CommanderStorm commented on GitHub (Feb 2, 2024): I don't know any reason why your mail server is timeouting these requests, but not when you send them with the same credentials from your local machine. I sort of suspect a networking issue or a copy and paste/differing configuration issue because sending mails works on my machine. You can try if you can contact the mail server via https://github.com/louislam/uptime-kuma/wiki/Troubleshooting or look into your mailservers logs

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@jspatel commented on GitHub (Feb 5, 2024):

I am running into same issue. As soon as I press test button for the SMTP mail, it throws error on docker console log. I am running 1.23.11.

Error: Connection timeout
    at SMTPConnection._formatError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:784:19)
    at SMTPConnection._onError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:770:20)
    at Timeout.<anonymous> (/app/node_modules/nodemailer/lib/smtp-connection/index.js:229:22)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7) {
  code: 'ETIMEDOUT',
  command: 'CONN'
}

I have checked the mail server and it is working fine. I also reset the password to ensure that it is not a typo.
I am using the hosted mail server provider and I have plenty of other emails in the same domain working fine. Uptime Kuma can't simply connect and send out the test email.

@jspatel commented on GitHub (Feb 5, 2024): I am running into same issue. As soon as I press test button for the SMTP mail, it throws error on docker console log. I am running 1.23.11. ``` Error: Connection timeout at SMTPConnection._formatError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:784:19) at SMTPConnection._onError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:770:20) at Timeout.<anonymous> (/app/node_modules/nodemailer/lib/smtp-connection/index.js:229:22) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) { code: 'ETIMEDOUT', command: 'CONN' } ``` I have checked the mail server and it is working fine. I also reset the password to ensure that it is not a typo. I am using the hosted mail server provider and I have plenty of other emails in the same domain working fine. Uptime Kuma can't simply connect and send out the test email.

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 5, 2024):

I think I was unclear.
Could you try via https://github.com/louislam/uptime-kuma/wiki/Troubleshooting this is a networking issue on the path to your mail server and/or give us more intel on how to reproduce this (mail provider).
Currently, I cannot reproduce the mail notifications not working…

@CommanderStorm commented on GitHub (Feb 5, 2024): I think I was unclear. Could you try via https://github.com/louislam/uptime-kuma/wiki/Troubleshooting this is a networking issue on the path to your mail server and/or give us more intel on how to reproduce this (mail provider). Currently, I cannot reproduce the mail notifications not working…

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@axiomcs78 commented on GitHub (Mar 18, 2024):

Mail notif. are not working here either. Trying gmail. What email provider(s) are you using or which ones are known to work?
After setting it up, immediately after clicking Save I get the error msg "querya etimeout". Also happens with an MS365 email address. (hmm, I no longer see the ability to create Email monitors)

@axiomcs78 commented on GitHub (Mar 18, 2024): Mail notif. are not working here either. Trying gmail. What email provider(s) are you using or which ones are known to work? After setting it up, immediately after clicking Save I get the error msg "querya etimeout". Also happens with an MS365 email address. (hmm, I no longer see the ability to create Email monitors)

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (May 17, 2024):

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions[bot] commented on GitHub (May 17, 2024): We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@nicopowa commented on GitHub (Nov 10, 2024):

Same error here, running Uptime Kuma and Docker MailServer running on the same machine.

Communications are blocked by ufw, which seems to be a known issue out there, lots of things to read before choosing the right conf.

[UFW BLOCK] IN=docker0 OUT= SRC={UPTIME_KUMA_CONTAINER_IP} DST={HOST_PUBLIC_IP} ... DF PROTO=TCP SPT=36832 DPT=465

EDIT : added this ufw rule and double checked all rules and listening ports, mail delivered :)

ufw allow from 172.17.0.0/16 to any port 465 proto tcp

@nicopowa commented on GitHub (Nov 10, 2024): Same error here, running Uptime Kuma and [Docker MailServer](https://docker-mailserver.github.io/docker-mailserver/latest/) running on the same machine. Communications are blocked by ufw, which seems to be a known issue out there, lots of things to read before choosing the right conf. `[UFW BLOCK] IN=docker0 OUT= SRC={UPTIME_KUMA_CONTAINER_IP} DST={HOST_PUBLIC_IP} ... DF PROTO=TCP SPT=36832 DPT=465` EDIT : added this ufw rule and double checked all rules and listening ports, mail delivered :) `ufw allow from 172.17.0.0/16 to any port 465 proto tcp`

deekerman commented

2026-02-28 03:17:38 -05:00

Author

Owner

@talaikis commented on GitHub (Jun 21, 2025):

AWS S3 doesn't work too while everything works fine elsewhere.

@talaikis commented on GitHub (Jun 21, 2025): AWS S3 doesn't work too while everything works fine elsewhere.