Before flaming me, please note I’ve read through nearly every post on these forums about Discourse + Mailjet, but nothing has answered my specific question. During the setup process, Discourse wants the following information: DISCOURSE_DEVELOPER_EMAILS — can be anything DISCOURSE_SMTP_ADDRESS — I’m using in-v3.mailjet.com, but this is just a guess! DISCOURSE_SMTP_PORT — 587 DISCOURSE_SMTP_USER_NAME — My Mailjet login name? DISCOURSE_SMTP_PASSWORD — My Mailjet login password? The three I am completely unsure about are: DISCOURSE_SMTP_ADDRESS DISCOURSE_SMTP_USER_NAME DISCOURSE_SMTP_PASSWORD Mailjet doesn’t include all these items in their UI in one place, and it’s really unclear what is supposed to go where. I have reached out to their support staff, but they replied with “After reviewing the information in the ticket, it has been determined that we will need to engage another group of colleagues.” … and then they disappeared for 48 hours. I’ve already set up the SPF and DKIM records for Mailjet, so all that stuff is in place, but I think the username and password are incorrect because /discourse-doctor suggests that’s the point of failure. If you can provide me with some clear insight here, I would be very grateful! Thank you.

I was testing this exact setup (1GB RAM + 2GB SWAP) and it fails 50% of the time during Ember build phase. You can either keep trying or bump to a $12 2GB RAM droplet. cc @david this is what we were discussing earlier this week.

Cross-linking this similar one - Upgrade from 3.2.0.beta3-dev to 3.2.0.beta3 failed due to out of memory - #9 by JammyDodger

[imagem] Falco: I was testing this exact setup (1GB RAM + 2GB SWAP) and it fails 50% of the time during Ember build phase. I’ve had two sites recently with 8GB of RAM and no swap that failed like this. (At least somewhere it failed with an exit 137). In both cases I added 2gb of swap and they worked.

Hopefully - for me - this can be regarded as a bug?

This is not a bug. Discourse requires what it requires, and if the necessary resources are not available, it cannot be installed. The “recalibration” that’s most likely necessary here is that we must adjust to a new, more expensive reality to rolling out Discourse installations. If you want to save money, you’ll need to do some fairly technical things from the command prompt to set up your environment to allow Discourse to install properly at the lower price point Droplet options.

I believe a change has been implemented to ameliorate this issue: [imagem] Upgrade from 3.2.0.beta3-dev to 3.2.0.beta3 failed due to out of memory Self-hosting Definitely, which is why we are gathering info here. It appears that tweaking our NODE_OPTIONS environment variable is all that is needed, so I’d guess that either a dependency of the app or a V8 change made our previous value there not work anymore. @david how this looks? https://github.com/discourse/discourse/pull/24850

I followed your suggestion and was able to install Discourse successfully on a $6 Droplet. However, my main issue now is I cannot seem to connect Mailjet properly, and as a result, I cannot get past the “Confirm Your Email” part of the setup process. Is there a way to bypass this until I can configure the Mailjet stuff successfully? Or do I need to sort out the Mailjet stuff first? (My issue is I have no way to see WHY the Mailjet stuff is failing. I’ve added SPF/DKIM and all that, but it’s still a no-go. Obviously, something is incorrect, but I have no indication about what that might be.)

Does the sending address match the one configured at Mailjet? It won’t send email for other addresses and is a pretty common mistake.

I am not using a Sender Address for Mailjet. Instead, I am using a Sender Domain (which opens up the use of nonexistent entities like noreply@mydomain.com). I cannot use the Sender Address because, technically, no emails exist on this domain (because I cannot do this reasonably with DigitalOcean). If I were to use a Sender Address, it would not match the domain and would therefore not work for transactional emails from Discourse (or WordPress). Bonus question: Do I need to add my subdomain—forum.mydomain.com—as a Sender Domain (separate from my root domain)?

By sender he means the address that Discourse is using to send. The “notification email address.” See Troubleshoot email on a new Discourse install

Configuração do Discourse + DigitalOcean + Mailjet

Suporte ao Produto Instalação

JammyDodger 12 Dezembro , 2023 19:11 23

Acredito que uma alteração foi implementada para melhorar este problema:

Tópico		Respostas	Vistas
Troubleshoot email on a new Discourse install Self-Hosting email , configuring , how-to	36	185847	27 Abril , 2026
Verification Email will not send due to errors caused by Docker filesystem Self-hosting email	23	7182	4 Setembro , 2015
If local logins are disabled Product Support	29	1216	17 Julho , 2026
Deploy Discourse without Docker Sysadmins unsupported-install , advanced-setup	33	2498	8 Janeiro , 2026
Discourse-app container starts then silently stops Self-hosting unsupported-install	40	4356	20 Setembro , 2022

Configuração do Discourse + DigitalOcean + Mailjet

Related topics