I’ve been self-hosting Discourse for many years, and had several instances happily configured and running on a fairly beefy machine. Today I noticed that one of my forums had gone down. The initial culprit looked to be lack of disk space, which I fixed. I then restarted the Discourse instance. How…

Yes that’s right, it’s the same problem … it started about two weeks ago.

Can you try both DISCOURSE_SMTP_ENABLE_START_TLS: false DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none ?

Are the first things I tried but still the same error SSL_connect returned=1 errno=0 state=error: certificate verify failed (Hostname mismatch)

[image] Falco: DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none Hey, I tried it with both the options. It still doesn’t work: DISCOURSE_SMTP_ADDRESS: REDACTED DISCOURSE_SMTP_PORT: 25 DISCOURSE_SMTP_USER_NAME: REDACTED DISCOURSE_SMTP_PASSWORD: REDACTED DISCOURSE_SMTP_ENABLE_START_TLS: false…

For me it has been a blocking bug for a long time … I recommend you to create a new temporary email address that has SMTP TLS support.

Could this be related to this gem [image] Install Discourse for development using Docker Developer Guides I met this problem too. And I fixed it by reverting this commit

I have the exact same problem. It started yesterday, when I upgraded (via rebuild) to 2.9.0.beta4 (a5779a7d0b). I made NO changes to app.yml, or anything else. Just a rebuild. I now have over 1,300 failed jobs. I’m seeing SSL errors in the logs (see below for screenshots), and I’m wondering if the…

I tried sending a message from inside the Discourse Docker container using curl. Once I made sure to specify plaintext SMTP and port 25, I can send email via the host just fine: $ cd /var/discourse/ $ sudo ./launcher enter app x86_64 arch detected. root@discourse-app:/var/www/discourse# curl smtp:/…

Bump, @pfaffman and/or @codinghorror . Do you think we may have a bug here, or something else?

@gunnar I moved your post here since this is the email issue you’re describing. I am not sure if the “post has already been taken” error is also being caused by this, but the details you gave about your email belong to this issue.

Email Hostname Certificate Mismatch Causing sidekiq Queue Overload, Severe Site Instability

Support Self-hosting

pfaffman (Jay Pfaffman) May 16, 2022, 12:14am 35

Could this be related to this gem

Topic		Replies	Views
E-mail sending stopped working after upgrade Self-hosting	2	818	May 29, 2022
Email not working (SSL_connect returned=1) Self-hosting	15	2673	June 15, 2022
Discourse with other websites, SMTP issue: End of file reached Self-hosting	7	2415	September 22, 2020
Troubleshoot email on a new Discourse install Self-Hosting email , configuring , how-to	36	183296	April 27, 2026
Issues with Discourse 3.5.0.beta2-dev - SMTP and Background Jobs Bug email	16	501	March 6, 2025

Email Hostname Certificate Mismatch Causing sidekiq Queue Overload, Severe Site Instability

Related topics