Obviously, this has something to do with my email configuration. I’m learning to setup my own Discourse instance, currently as a droplet in Digital Ocean. I have the instance setup, and it’s available at jordanviolet.dev.
I’ve gone through the troubleshooting doc with no luck:
I am looking to use my Google Workspace (gmail) account as my email provider. Here are my smtp email settings:
## TODO: List of comma delimited emails that will be made admin and developer
## on initial signup example 'user1@example.com,user2@example.com'
DISCOURSE_DEVELOPER_EMAILS: 'jordan@violetfamily.com'
## 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-relay.gmail.com
DISCOURSE_SMTP_PORT: 587
DISCOURSE_SMTP_USER_NAME: myemail@violetfamily.com
DISCOURSE_SMTP_PASSWORD: "myemailpassword"
#DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true)
DISCOURSE_SMTP_DOMAIN: violetfamily.com
DISCOURSE_NOTIFICATION_EMAIL: jordan@violetfamily.com
## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
LETSENCRYPT_ACCOUNT_EMAIL: me@example.com
I also believe I followed Google’s docs correctly for SMTP relay:
Here are my settings from my Workspace > Gmail > Routing settings: