Sorry for another redundant question, as I can see there are many similar support requests to this, eg: Email Notifications Failing after Update , but our error message is slightly different: “certificate verify failed (unable to get local issuer certificate)” This is after the update on May 11t…

@RGJ I tried running openssl s_client -connect smtp.mydomain.info:25 -starttls smtp -showcerts 2>&1|grep "depth=0" but it doesn’t show any other domains, it just says the same error as sidekiq: “unable to get local issuer certificate” and a bunch of other stuff. I tried changing the app.yml mail …

There are three possible causes for this: expired certificate hostname in the certificate is different than the hostname you’re connecting to no certificate at all It looks like you are experiencing the latter one. The only resolution is to make sure you have a correctly configured SMTP server, s…

Thanks @RGJ - but why did this issue only begin after upgrading to version 2.9.0? Is it because STARTTLS is being stricter about enforcing this requirement. Nothing has changed for our mail relay or in the app.yml mail configuration. The site’s IP is whitelisted with the mail relay which is maintain…

Because there was a change where Discourse upgraded to Rails 7 between 2.9.0.beta3 and beta4, which triggered this. See Email Hostname Certificate Mismatch Causing sidekiq Queue Overload, Severe Site Instability - #47 by RGJ

Our IT dept says, “there’s nothing wrong with certificates [for the mail relay] all are active and properly configured to be used with smtp service. Second - I haven’t heard of any problems from any other services/clients that are using this mail relay.” :cry:

IT has created a new email account using office365 onmicrosoft, but I am still having issues. Now I get either ReadTimeout or SMTPAuthenticationError: Unrecognized authentication type my current config: DISCOURSE_SMTP_ADDRESS: smtp.office365.com DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: m…

@RGJ I want to thank everyone for their help. I finally, finally have this resolved. The tweak for office365 is to use DISCOURSE_SMTP_AUTHENTICATION: login. The offce365 smtp server and port config are smtp.office365.com:587 with STARTTLS enabled, which is the default anyway. And the username is t…

We are experiencing the very same issue here with a PROPERLY configured SMTP server used by dozens of other services. The SMTP server employs a wildcard certificate issued byt Let’s Encrypt. The error says:" (unable to get local issuer certificate)"

I think that it’s a bug as described at Disabling starttls or certificate verification does not work any more Except you say that you have a valid cert. So I might be wrong.

try to check the domain name using the commands recommended by @RGJ openssl s_client -connect smtp.mydomain.info:25 -starttls smtp -showcerts 2>&1|grep "depth=0" make sure your domain matches the certificate returned from openssl if any. Also check this thread “Email Hostname Cert Mismatch Causin…

최신 업데이트 후 이메일 작업 실패, 인증서 검증 실패 (로컬 발급자 인증서를 가져올 수 없음)

지원 자체 호스팅

RGJ (Richard - Communiteq) 5월 25, 2022, 6:13오전 2

This is the same problem as Email Hostname Certificate Mismatch Causing sidekiq Queue Overload, Severe Site Instability

글		댓글	조회수
Emails not working after upgrade: certificate verify failed Self-hosting	1	1289	5월 13, 2022
E-mail sending stopped working after upgrade Self-hosting	2	845	5월 29, 2022
Emails stopped working, failing after upgrade Self-hosting	1	624	5월 19, 2022
Email Hostname Certificate Mismatch Causing sidekiq Queue Overload, Severe Site Instability Self-hosting	63	6351	9월 28, 2023
Email Notifications Failing after Update Self-hosting email	3	844	10월 31, 2019

최신 업데이트 후 이메일 작업 실패, 인증서 검증 실패 (로컬 발급자 인증서를 가져올 수 없음)

Related topics