Net::ReadTimeout | Confirmation email not sending

Product Support Self-hosting

AI-generated summary

KingEZFLOW is unable to complete Discourse installation because confirmation emails fail to send, returning a Net::ReadTimeout error when running ./discourse-doctor. Their SMTP settings (using Roundcube with no-reply@REDACTED.gg) work elsewhere but not in Discourse. Heliosurge questions whether the SMTP username is actually the Roundcube login (not just a no-reply address) and suggests checking Roundcube’s forum or video guides for SMTP setup. KingEZFLOW confirms the credentials are correct and Roundcube supports SMTP, but Discourse still won’t connect. Heliosurge recommends checking Sidekiq and Roundcube logs, but KingEZFLOW found nothing useful. Heliosurge shares AI-generated instructions for configuring Roundcube as an SMTP server for Discourse — though this appears to misunderstand the setup (it describes using Discourse as SMTP for Roundcube, not vice versa). KingEZFLOW clarifies they’re stuck at admin creation because email verification fails, preventing access to the admin panel. Heliosurge advises temporarily switching to Brevo’s free tier to complete setup, then attempting Roundcube again afterward.

1

Got discourse installed and am trying to finish the installation process with the confirm email screen and the email isn’t being sent out. All of the creds for my SMTP work as I can login with the creds using anything else but discourse

image
image1007×302 16.2 KB

My mail server is roundcube.
When I use discourse-doctor it outputs: Net::ReadTimeout

app.yml

  ## TODO: The SMTP mail server used to validate new accounts and send notifications
  # SMTP ADDRESS, username, and password are required
  # WARNING the char '#' in SMTP password can cause problems!
  DISCOURSE_SMTP_ADDRESS: smtp.REDACTED.gg
  DISCOURSE_SMTP_PORT: 465
  DISCOURSE_SMTP_USER_NAME: no-reply@REDACTED.gg
  DISCOURSE_SMTP_PASSWORD: REDACTED
  #DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)
  #DISCOURSE_SMTP_DOMAIN: REDACTED.gg    # (required by some providers)
  DISCOURSE_NOTIFICATION_EMAIL: no-reply@REDACTED.gg    # (address to send notifications from)
2

not getting confirmation mail.

3

Anyone know how I can fix?

4

DISCOURSE_SMTP_USER_NAME: no-reply@REDACTED.gg

Is “no-reply@REDACTED.gg”

Is this your Roundcube SMTP login?

This Field is not your “noreply@yourdomain.com”. It will be your Roundcube login and password.

Does Roundcube support being a SMTP server?

Brevo com does have a free tier of 300 emails/day

5

yes, “no-reply@REDACTED.gg” is my login user, and roundcube does support SMTP

6

Have you tried Roundcube’s forum?

A general search I did came up with a video adding an SMTP to Roundcube

7

I already have SMTP setup for roundcube, and I use SMTP for it on a daily for my other applications. It’s just that discourse refuses to connect to it

8

Does the test email work during setup? Have you checked discourse logs ie sidekick and Roundcube logs?

9

Didn’t find anything in roundcube logs. I ran ./discourse-doctor and it output “Net::ReadTimeout”. Not sure where to check logs for discourse

10

Often on one of the instances I help manage. On the Dashboard for discourse you might see Sidekiq jobs failed. In my case this was due to the client not maintaining there SMTP account package.

Doing a search on discourse here there are a few topics regarding Roundcube but nothing that looks helpful.

What about the Roundcube support & forum?

I asked google Gemini AI. So this may help but don’t know.

11

Roundcube is already setup for SMTP use as I use it for my other websites, and I can’t access the Discourse admin panel as I can’t finish the last bit of the installation (where I have to create the admin account and verify the email) as when I try and verify the admin email no email gets sent due to Net::ReadTimeout

12

Okay. I would recommend using brevo.com free tier to complete setup.

After completing then try swapping to Roundqube.