In a troubleshooting thread titled “Discourse aws EC2 G Suite troubleshoting,” a.prisniak reports issues configuring SMTP for a fresh Discourse installation on AWS EC2 using a G Suite corporate email. Despite trying various settings — including smtp.gmail.com on ports 465 and 587 — the setup failed during initial configuration. codinghorror suggests reviewing the official email troubleshooting guide and notes that using smtp.gmail.com may be incorrect for custom G Suite domains, recommending smtp-relay.gmail.com instead. a.prisniak confirms success after switching to port 587 and removing quotation marks around the SMTP password — which were inadvertently added during bootstrapping. The fix resolved the SMTP authentication issue, allowing the Discourse setup to complete. The thread highlights common pitfalls when integrating G Suite SMTP with Discourse, particularly around port selection and password formatting.
I’ve fresh installation of discourse on amazon EC2 instance and have been configured SMTP with G suite corporate account. But can’t finish initial settings because of SMTP. I’ve tried different smtp settings but with no success.
Thx Jeff, I’ve configured SMPT as it shown in google instructions. And I’ve also try smtp-relay.gmail.com and smtp.gmail.com ports 465, 587.
My email not a ****@gmail.com. I’m using exact my G Suite email account.
So, finally I did it!
DISCOURSE_SMTP_ADDRESS: smtp.gmail.com
DISCOURSE_SMTP_PORT: 465 → And I’ve also changed port to 587
DISCOURSE_SMTP_USER_NAME: my@corporate.email
DISCOURSE_SMTP_PASSWORD: “mypassword” ← error here. I’ve removed quotes and all works just fine.
DISCOURSE_SMTP_ENABLE_START_TLS: true
By the way quotes where added while bootstrapping.