Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Tried different SMTP services and still cannot receive transactional emails #4621

Closed
pshemek opened this issue Dec 18, 2024 · 10 comments · Fixed by #4649
Closed

[Bug]: Tried different SMTP services and still cannot receive transactional emails #4621

pshemek opened this issue Dec 18, 2024 · 10 comments · Fixed by #4649

Comments

@pshemek
Copy link

pshemek commented Dec 18, 2024

Error Message and Logs

Whatever I do, I cannot get transactional emails via SMTP to work even on fresh install on Hetzner.
I also don't know where the logs, if any, are located to see what is happening.

Steps to Reproduce

  1. Spin up a new server (tried CAX21 and CPX11) on Hetzner
  2. Clean install Coolify
  3. Go to Transactional Email settings and set up SMTP, i.e.:
    smtp.resend.com
    resend
    587
    TLS
  4. Send test email and check if it is received.

NOTE: It's all about SMTP; emails via Resend API do work

Example Repository URL

No response

Coolify Version

v4.0.0-beta.379

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

  1. On the other hand, when I installed Uptime Kuma, it sends well via the same SMTP.
  2. I also have a similar setup on other VPS with Dokploy and notifications with the same SMTP do work there. (Different server provider than Hetzner although uses Hetzner under the hood)

EDIT: 587 SSL do work. Only 587 TLS doesn't. Kudos to @Drunkenpilot for the tip.

@pshemek pshemek added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Dec 18, 2024
@fma965
Copy link

fma965 commented Dec 19, 2024

I had this issue with mailgun when using TLS despite working elsewhere, i changed it to SSL and it worked despite other applications using TLS.

@pshemek
Copy link
Author

pshemek commented Dec 19, 2024

Unfortunately, Hetzner blocks outgoing 465 for fresh accounts so I'll have to wait.
However, would be great if 587 worked...

@Drunkenpilot
Copy link

Unfortunately, Hetzner blocks outgoing 465 for fresh accounts so I'll have to wait. However, would be great if 587 worked...

Tried Brevo's SMTP with port 587 + ssl. It worked on an hetzner vps.

@nettags
Copy link

nettags commented Dec 19, 2024

Same problem: 587 TLS does not work since the (automatic) update to v4.0.0-beta.379. Also using Hetzner, but transactional emails worked fine before the update.

@Drunkenpilot
Copy link

Same problem: 587 TLS does not work since the (automatic) update to v4.0.0-beta.379. Also using Hetzner, but transactional emails worked fine before the update.

Have you already try 587 with SSL ? Before v4.0.0-beta.379, we use Mailjet SMTP with 587 + TLS. After the update we can only made it worked by using Brevo with 587 + SSL.

@fma965
Copy link

fma965 commented Dec 19, 2024

now that you mention this, this is exactly what I had to do, I was slightly wrong on my earlier post

@nettags
Copy link

nettags commented Dec 19, 2024

Same problem: 587 TLS does not work since the (automatic) update to v4.0.0-beta.379. Also using Hetzner, but transactional emails worked fine before the update.

Have you already try 587 with SSL ? Before v4.0.0-beta.379, we use Mailjet SMTP with 587 + TLS. After the update we can only made it worked by using Brevo with 587 + SSL.

Yes, 587 + SSL is working, 587 + TLS not anymore. Thanks for the hint!

@peaklabs-dev peaklabs-dev self-assigned this Dec 23, 2024
@peaklabs-dev peaklabs-dev added ✅ Done Issues that are fixed and a PR is ready to be merged. and removed 🔍 Triage Issues that need assessment and prioritization. ✅ Done Issues that are fixed and a PR is ready to be merged. labels Dec 23, 2024
@peaklabs-dev peaklabs-dev added 🐞 Confirmed Bug Verified issues that have been reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged. labels Dec 23, 2024
@peaklabs-dev
Copy link
Member

A fix for this issue has been implemented and will be available in an upcoming release. Thank you for your patience.

@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Dec 23, 2024
@github-actions github-actions bot removed 🐛 Bug Reported issues that need to be reproduced by the team. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged. labels Dec 27, 2024
@shadowoff09
Copy link

So we have to wait for the 4.0.0 stable release to have a fix?

@peaklabs-dev
Copy link
Member

No the fix is live in v4.0.0-beta.380

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants