Custom SMTP Didn't Send any Email
I have config my custom SMTP to send email
first it work last email that was send is last week ago than it didn't send any email from that on
I have check
- Is my email SMTP provider still work?
- Yes It still work I can still manually sent with NOVU but it not work on my zitadel some how
My Zitadel Version is v3.3.0
8 Replies
Hi @เรย์โคชิมะ, thanks for reaching out! Does NOVU have logs that you can check for the email delivery service? Are you using a paid production environment or a demo one? I saw in their documentation that they limit demo envs to 300 emails. Please let me know if you can check the above.
I'm using thier free version on website using same provider with same username and password
now just try to send it again and it work but for zitadel it still say same thing
Hi @เรย์โคชิมะ,
The Console’s “Test” button calls POST /email/smtp/_test (gRPC-web). If the browser doesn’t receive any HTTP status (e.g. a reverse-proxy closed the stream, or ZITADEL returned an internal error the proxy couldn’t translate) the JS client maps that to code 0 with the “400 or 500 level” text.
A very similar symptom was discussed in GitHub issue #9372 where the culprit was an h2c mis-configuration in the proxy layer.
The real root cause would be shown in ZITADEL’s server log; the UI just loses the details. Typical log lines look like
level=error msg="EMAIL-r4e1f dial tcp: lookup smtp.example.com: no such host".
Are you on Zitadel cloud, or a self-hosted instance? we will need to take a different approach for troubleshooting depending on your architecture, but some steps you can already take:
- If you are self-hoster, check container logs – the real SMTP error is in there. You can run something like:
docker compose logs --tail=200 zitadel | grep EMAIL-
- Verify DNS + outbound port 465/587 reachability from the container.
- If you created the SMTP provider long ago, or upgraded your Zitadel instance afterwards, delete the provider & re-add it. I would advice to try this anyway.
Please let me know how that goes.GitHub
Self hosted - ERROR Http response at 400 or 500 level · zitadel zi...
I've set up the self hosted zitadel using docker compose. It is set up behind a traefik reverse proxy with a custom letsencrypt cert. There are no errors in the docker stdout, but I'm getti...
Hello I have try to find error and it not found
but at least I found it
my app is deploy in DigitalOcean cloud
and DigitalOcean is block smtp port
so because of that the email will not sent?
https://www.digitalocean.com/community/questions/smtp-587-ports-is-closed
SMTP 587 ports is closed | DigitalOcean
in-v3.mailjet.com 587 Trying 104.199.96.85... Please unban sudo ufw status verbose Status: active Logging: on (low) Default: deny (incoming...
but for novu I using cloud version not my self hosting
I got a solution
setup a HTTP provider point to n8n as one of my email adapter and send from that
Hi @raykoshima thanks for getting back to me, I'm glad you were able to find a workaround!
my app is deploy in DigitalOcean cloud ... but for novu I using cloud version not my self hostingI still do not know what was going on with novu. Zitadel Cloud is hosted on GCP, and I know for sure that GCP does not block outboud connections on port 587. In fact, I'm using mailtrap as my custom SMTP provider on port 587 in Zitadel cloud right now, and emails get sent. In any case, I'm just glad that you are no longer blocked by this 🙇♂️ please let me know if you have any other questions.
where I can find a email template?
Hey @raykoshima, when using the HTTP provider, you will get a JSON payload like the one described in the docs. There is no predefined email template, you will have to create your templates for each email type and use the received data in "templateData" and "args".
ZITADEL Docs
ZITADEL can send messages to users via different notification providers, such as SMS, SMTP, or Webhook (HTTP Provider).