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

Certificate error for e-mail #2895

Open
RumenBlack84 opened this issue Apr 20, 2024 · 2 comments
Open

Certificate error for e-mail #2895

RumenBlack84 opened this issue Apr 20, 2024 · 2 comments
Labels
needs-triage Needs to be triaged by a developer and assigned a release

Comments

@RumenBlack84
Copy link

What happened?

I am trying to use my protonmail bridge to send e-mails. However due to the nature of how the bridge works it's certificate is invalid for external use. Due to this invalid certificate I cannot send emails using kavita. Is there a way to bypass the certificate check for sending e-mails?

I'm not sure if this would be considered an issue report or a feature request.

What did you expect?

A method to bypass certificate checking for sending emails.

Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists.

0.8.0 - Stable

What operating system is Kavita being hosted from?

Docker (Dockerhub Container)

If the issue is being seen on Desktop, what OS are you running where you see the issue?

None

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Chrome

If the issue is being seen on Mobile, what OS are you running where you see the issue?

None

If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?

No response

Relevant log output

No response

Additional Notes

No response

@RumenBlack84 RumenBlack84 added the needs-triage Needs to be triaged by a developer and assigned a release label Apr 20, 2024
@DieselTech
Copy link
Collaborator

There is no concept of certificates in Kavita for email. That sounds like something specifically for proton bridge that would need to be configured.

@nachfuellbar
Copy link

nachfuellbar commented Apr 23, 2024

I've gotten a similiar error with my own Mail Server.
In Kavita's log i got this error. Seems like it wants a CRL even if the certificate is in the trust store.
The second error with self signed certificate is possibile to mitigate when importing the certificate of the CA.

I don't know if it's the same for protonmail bridge but as far as i can see (without actually testing) the issue should be the same.

The server's SSL certificate could not be validated for the following reasons:
 • The server certificate has the following errors:
   • unable to get certificate CRL
   • unable to get certificate CRL
 • The root certificate has the following errors:
   • self signed certificate in certificate chain

PS: would be great to have an possibility to disable the certificate check for Mail Server as they often use self signed ones (even in the internet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Needs to be triaged by a developer and assigned a release
Projects
None yet
Development

No branches or pull requests

3 participants