Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow Self-Signed Certificates not respected

See original GitHub issue

Description

When setting up email notifications, the check box for “Allow Self-Signed Certificates” is checked. However no emails are sent, with the error:

2022-07-18T22:57:35.826Z [error][Notifications]: Error sending email notification
{
  "errorMessage":"self signed certificate",
  "recipient":"xerxes",
  "subject":"Test Notification",
  "type":"TEST_NOTIFICATION"
}

For reference, these exact settings work with another service I have, i.e. another service can send emails using a self-signed certificate

Version

v1.1.0

Steps to Reproduce

Must use an email server using a self-signed certificate.
Settings
Notifications
Email
Check “Allow Self-Signed Certificates”
Send test email

Screenshots

Screenshot from 2022-07-18 18-02-45

Logs

{
 "errorMessage": "self signed certificate",
 "recipient": "xerxes",
 "subject": "Test Notification",
 "type": "TEST_NOTIFICATION"
}

Platform

desktop

Device

Desktop

Operating System

Pop!_OS 22.04 LTS

Browser

Firefox 102.0.1 (64-bit)

Additional Context

Using docker from fallenbagel/jellyseerr:develop

Code of Conduct

I agree to follow Overseerr’s Code of Conduct

Issue Analytics

State:
Created a year ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

dawsoc2commented, Jul 22, 2022

Disabling TLS entirely at least allows me to send emails. The protonmail-bridge running on a separate container is exactly my situation; thanks for finding this.

0reactions

Fallenbagelcommented, Jul 23, 2022

Closing this issue then c:

Top Results From Across the Web

Why are self signed certificates not trusted and is there a way ...

Self-signed certificates are inherently not trusted by your browser because a certificate itself doesn't form any trust, ...

What is a Self-Signed Certificate? Advantages, Risks ...

Compromised self-signed certificates can pose many security challenges, since attackers can spoof the identity of the victim. Unlike CA-issued ...

How can I make git accept a self signed certificate?

To permanently accept a specific certificate. Try http.sslCAPath or http.sslCAInfo . Adam Spiers's answer gives some great examples. This is the most secure ......

Cybersecurity Risks of Using Self-Signed Certificates

Dangers of Using Self-Signed Certificates · Root certificates can be leaked · Certificate warnings can be ignored · Brand reputation damage.

The Dangers of Self-Signed Certificates - Okta Developer

Self -Signed certificates are free, but not without cost. In this post you'll learn all about the dangers of self-signed certificates.