Cloudron Forum

Hello everyone,

I am currently trying to setup a send email node in n8n.
I have done what was suggested here and I created a specific user for this. I have also setup a mailbox associated to that user.

Outbound emails work fine already with any apps (relay through mailjet).
I have added the new user email as a sender in mailjet config.

I have used the credentials from that new user to setup the n8n SMTP account.
I use port 587 and mail.<domain> as the host.
SSL is disabled and STARTTLS is enabled.

I have also added the client host name as the n8n hostname.

Is there a better way to do this now? (this linked post is from 2021, so maybe this information is outdated).
Is there something I missed?

Thank you all for your help

Ok, so after looking into open ports a bit more, it turns out that there is nothing listening on port 587. As such, there is no SMTP server running or listening to any port whatsoever. I figure that an SMTP server may only start running if I enable incoming emails (setting which was not enabled, purposefully). When I enabled incoming email setting, sudo netstat -tlnp | grep 587 was finally returning something and n8n configuration worked fine.

So to sum up, if my understanding is correct, when only using outbound mail, there isn't an actual SMTP server running, but only some kind of abstraction that containerized apps can use to send email directly through the mail relay (the internals of this are fuzzy to me...), so I need to enable incoming emails in order to send emails...

But I'm glad I was at least able to make this work before going into 2026. Thanks for the help and for putting me on the right path here.

Thank you for all the great work you do Cloudron Team, and wishing you all the best for the new year :).

Hello everyone,

I have set up the change detection application to monitor changes on some websites. When those changes occur, I would like to send a notification to an ntfy service (also hosted on the same cloudron).

ChangeDetection support such feature with apprise. So I can put this in settings > Notifications and it should work: ntfys://<token>@<ntfy_hostname>/changedetection

However, I am getting the following errors:

2024/09/09 15:08:56,000 - SENDING - null
2024-09-09 15:09:01,045 - DEBUG - Socket Exception: HTTPSConnectionPool(host='<ntfy_hostname>', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f723024ba90>, 'Connection to <ntfy_hostname> timed out. (connect timeout=4.0)'))
2024-09-09 15:09:01,045 - WARNING - A Connection error occurred sending ntfy:https://<ntfy_hostname> notification.
2024-09-09 15:08:56,706 - DEBUG - ntfy Headers: {'User-Agent': 'changedetection.io', 'Authorization': 'Bearer <token>', 'Content-Type': 'application/json', 'X-Icon': 'https://raw.githubusercontent.com/dgtlmoon/changedetection.io/master/changedetectionio/static/images/avatar-256x256.png'}
2024-09-09 15:08:56,706 - DEBUG - ntfy Payload: {'topic': 'changedetection', 'title': 'ChangeDetection.io Notification - https://changedetection.io/CHANGELOG.txt', 'message': 'https://changedetection.io/CHANGELOG.txt had a change.\n---\n\n---'}
2024-09-09 15:08:56,706 - DEBUG - ntfy POST URL: https://<ntfy_hostname>(cert_verify=True)
2024-09-09 15:08:56,705 - DEBUG - Loaded ntfy URL: ntfys://t...3@<ntfy_hostname>/changedetection?priority=default&mode=private&image=yes&auth=token&avatar_url=https%3A%2F%2Fraw.githubusercontent.com%2Fdgtlmoon%2Fchangedetection.io%2Fmaster%2Fchangedetectionio%2Fstatic%2Fimages%2Favatar-256x256.png&format=text&overflow=upstream&rto=4.0&cto=4.0&verify=yes

It's worth noting that I can publish notifications without any issue from ntfy client directly. I have also tried with apprise CLI, and it also works fine:
apprise -vv -t "Test Title" -b "Test Body" ntfys://<token>@<hostname>/changedetection

My cloudron is hosted on a server at home and I have a pihole for local DNS on the same network.

Could I please get some help to troubleshoot this issue?

Thank you

The update to 8.0.5 alone made it work! Thank you @joseph and @girish!