starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #1264] Error: Failed to send the confirmation email #352

New issue

Closed

opened 2026-02-26 18:46:38 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 18:46:38 +03:00

Owner

Originally created by @mnbro on GitHub (Aug 1, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1264

Issue Description

Hi,

I 've just deployed a new instance of documenso but Im not able to send any email(not even the confirmation email).

I receive the next error:

[JOBS]: Job send.signup.confirmation.email failed Error: Failed to send the confirmation email at u (/app/apps/web/.next/server/chunks/267.js:1:19105) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.handler (/app/apps/web/.next/server/chunks/267.js:1:14158) at async /app/apps/web/.next/server/chunks/267.js:1:10229

Here are my SMTP settings:

  NEXT_PRIVATE_SMTP_TRANSPORT: "smtp-auth"
  NEXT_PRIVATE_SMTP_HOST: "smtp.sendgrid.net"
  NEXT_PRIVATE_SMTP_PORT: 587
  NEXT_PRIVATE_SMTP_SECURE: "true"
  NEXT_PRIVATE_SMTP_USERNAME: "apikey"
  NEXT_PRIVATE_SMTP_PASSWORD: "xxxx"
  NEXT_PRIVATE_SMTP_FROM_NAME: "XXXX"
  NEXT_PRIVATE_SMTP_FROM_ADDRESS: "XXXXX"

I've tried also with other mail providers and also with different ports/TLS on/off but I get the same error.

Is there something obvious that I'm missing?

Steps to Reproduce

Create a new "Sign-up"

Expected Behavior

I should be able to send an email.

Current Behavior

No email is being sent.

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

No response

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @mnbro on GitHub (Aug 1, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1264 ### Issue Description Hi, I 've just deployed a new instance of documenso but Im not able to send any email(not even the confirmation email). I receive the next error: `[JOBS]: Job send.signup.confirmation.email failed Error: Failed to send the confirmation email at u (/app/apps/web/.next/server/chunks/267.js:1:19105) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.handler (/app/apps/web/.next/server/chunks/267.js:1:14158) at async /app/apps/web/.next/server/chunks/267.js:1:10229` Here are my SMTP settings: NEXT_PRIVATE_SMTP_TRANSPORT: "smtp-auth" NEXT_PRIVATE_SMTP_HOST: "smtp.sendgrid.net" NEXT_PRIVATE_SMTP_PORT: 587 NEXT_PRIVATE_SMTP_SECURE: "true" NEXT_PRIVATE_SMTP_USERNAME: "apikey" NEXT_PRIVATE_SMTP_PASSWORD: "xxxx" NEXT_PRIVATE_SMTP_FROM_NAME: "XXXX" NEXT_PRIVATE_SMTP_FROM_ADDRESS: "XXXXX" I've tried also with other mail providers and also with different ports/TLS on/off but I get the same error. Is there something obvious that I'm missing? ### Steps to Reproduce Create a new "Sign-up" ### Expected Behavior I should be able to send an email. ### Current Behavior No email is being sent. ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] _No response_ ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [X] I have searched the existing issues to make sure this is not a duplicate. - [X] I have provided steps to reproduce the issue. - [X] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [X] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:46:38 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:46:39 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 1, 2024):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Aug 1, 2024): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:46:39 +03:00

Author

Owner

@mnbro commented on GitHub (Aug 1, 2024):

Not adding NEXT_PRIVATE_SIGNING_PASSPHRASE will result in this kind of error.

@mnbro commented on GitHub (Aug 1, 2024): Not adding `NEXT_PRIVATE_SIGNING_PASSPHRASE` will result in this kind of error.

kerem commented

2026-02-26 18:46:39 +03:00

Author

Owner

@vinybk commented on GitHub (Aug 8, 2024):

Hello! I have the same problem and couldn't solve it so far. Any other ideas?

@vinybk commented on GitHub (Aug 8, 2024): Hello! I have the same problem and couldn't solve it so far. Any other ideas?

kerem commented

2026-02-26 18:46:39 +03:00

Author

Owner

@lhjt commented on GitHub (Aug 9, 2024):

I had this issue - turns out I was missing the NEXT_PRIVATE_SMTP_SECURE=true in my environment variables. Hope this might work for you @viniciusbrun-dev

@lhjt commented on GitHub (Aug 9, 2024): I had this issue - turns out I was missing the `NEXT_PRIVATE_SMTP_SECURE=true` in my environment variables. Hope this might work for you @viniciusbrun-dev

kerem commented

2026-02-26 18:46:39 +03:00

Author

Owner

@mngsgoncalves commented on GitHub (Jul 3, 2025):

I'm not able to send the confirmation e-mail as well - the password recovery one works just fine.

@mngsgoncalves commented on GitHub (Jul 3, 2025): I'm not able to send the confirmation e-mail as well - the password recovery one works just fine.

kerem referenced this issue

2026-02-26 19:30:58 +03:00

[PR #352] [CLOSED] feat: Add email validation to ForgotPassword #903

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#352

No description provided.

Rows
Columns