github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-07 21:30:36 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #264] self-signed certificate error when attempting to send an email #10127

New Issue
Closed
opened 2026-05-06 13:11:38 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-05-06 13:11:38 -05:00
Owner
Copy Link

Originally created by @Nightreaper77 on GitHub (Mar 2, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/264

When attempting to send an email after configuring SMTP, I am getting the following error:

2025-02-22T22:27:34.217Z [error]: self-signed certificate
Stack: Error: self-signed certificate
    at TLSSocket.onConnectSecure (node:_tls_wrap:1677:34)
    at TLSSocket.emit (node:events:518:28)
    at TLSSocket._finishInit (node:_tls_wrap:1076:8)
    at ssl.onhandshakedone (node:_tls_wrap:862:12)
    at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17) {"code":"ESOCKET","command":"CONN"}

I'm using ProtonMail Bridge as my SMTP server (unofficial docker container here: shenxn/protonmail-bridge-docker)

Relatively confident that the SMTP server is setup correctly, as I'm using the same configuration for other services like Nextcloud and they are working fine.

Here's my smtp configuration from config/config.yml:

email:
    smtp_host: "ip_address"
    smtp_port: 1025
    smtp_user: "username"
    smtp_pass: "password"
    no_reply: "email(same as username)"
    smtp_secure: false

ProtonMail Bridge is meant to use STARTTLS, which is normally configured as insecure, but I did try smtp_secure as well and got a TLS version mismatch (as expected).

Since it's a self-signed cert error, I imagine a config option could be added to ignore certificate warnings, but not sure.

Originally created by @Nightreaper77 on GitHub (Mar 2, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/264 When attempting to send an email after configuring SMTP, I am getting the following error: ``` 2025-02-22T22:27:34.217Z [error]: self-signed certificate Stack: Error: self-signed certificate at TLSSocket.onConnectSecure (node:_tls_wrap:1677:34) at TLSSocket.emit (node:events:518:28) at TLSSocket._finishInit (node:_tls_wrap:1076:8) at ssl.onhandshakedone (node:_tls_wrap:862:12) at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17) {"code":"ESOCKET","command":"CONN"} ``` I'm using ProtonMail Bridge as my SMTP server (unofficial docker container here: shenxn/protonmail-bridge-docker) Relatively confident that the SMTP server is setup correctly, as I'm using the same configuration for other services like Nextcloud and they are working fine. Here's my smtp configuration from config/config.yml: ``` email: smtp_host: "ip_address" smtp_port: 1025 smtp_user: "username" smtp_pass: "password" no_reply: "email(same as username)" smtp_secure: false ``` ProtonMail Bridge is meant to use STARTTLS, which is normally configured as insecure, but I did try smtp_secure as well and got a TLS version mismatch (as expected). Since it's a self-signed cert error, I imagine a config option could be added to ignore certificate warnings, but not sure.
GiteaMirror commented 2026-05-06 13:11:41 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Mar 3, 2025):

We use Nodemailer under the hood to send emails. I found this article that shows the following in the config.

tls: {
  rejectUnauthorized: false
}

Wondering if you think this would do the trick? I can expose this via the config file for you to test in the next release.

<!-- gh-comment-id:2693007897 --> @miloschwartz commented on GitHub (Mar 3, 2025): We use Nodemailer under the hood to send emails. I found [this article](https://dev.to/polluterofminds/how-to-use-protonmail-with-nodemailer-5c4l) that shows the following in the config. ```typescript tls: { rejectUnauthorized: false } ``` Wondering if you think this would do the trick? I can expose this via the config file for you to test in the next release.
GiteaMirror commented 2026-05-06 13:11:46 -05:00
Author
Owner
Copy Link

@Nightreaper77 commented on GitHub (Mar 3, 2025):

Yeah that definitely looks like the correct option. I'll test on next release. Thanks for the quick reply!

<!-- gh-comment-id:2693022890 --> @Nightreaper77 commented on GitHub (Mar 3, 2025): Yeah that definitely looks like the correct option. I'll test on next release. Thanks for the quick reply!
GiteaMirror commented 2026-05-06 13:11:49 -05:00
Author
Owner
Copy Link

@Nightreaper77 commented on GitHub (Mar 3, 2025):

Built from dev branch and confirmed that it does indeed fix the issue. Thanks!

<!-- gh-comment-id:2693224020 --> @Nightreaper77 commented on GitHub (Mar 3, 2025): Built from dev branch and confirmed that it does indeed fix the issue. Thanks!
GiteaMirror commented 2026-05-06 13:11:50 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Mar 3, 2025):

Awesome! Just fixed the typo in the config variable name.

<!-- gh-comment-id:2693245262 --> @miloschwartz commented on GitHub (Mar 3, 2025): Awesome! Just fixed the typo in the config variable name.
GiteaMirror commented 2026-05-06 13:11:52 -05:00
Author
Owner
Copy Link

@reg98643t commented on GitHub (Jul 7, 2025):

Sorry to resurrect this thread, but what do I put in my config.yml to make this work? I have the same issue with PM Bridge.

Edit: nevermind, if anyone stumbles on this it's

smtp_tls_reject_unauthorized: false

<!-- gh-comment-id:3046734976 --> @reg98643t commented on GitHub (Jul 7, 2025): Sorry to resurrect this thread, but what do I put in my config.yml to make this work? I have the same issue with PM Bridge. Edit: nevermind, if anyone stumbles on this it's > smtp_tls_reject_unauthorized: false
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#10127
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?