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…

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

[afbeelding] 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 …

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 sav…

I believe a change has been implemented to ameliorate this issue: [afbeelding] 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 …

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 confi…

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). …

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

Discourse + DigitalOcean + Mailjet instellen

Ondersteuning Installatie

JammyDodger 12 december 2023 om 19:11 23

I believe a change has been implemented to ameliorate this issue:

Topic		Antwoorden	Weergaven
Troubleshoot email on a new Discourse install Self-Hosting email , configuring , how-to	36	183242	27 april 2026
Verification Email will not send due to errors caused by Docker filesystem Self-hosting email	23	7035	4 september 2015
If local logins are disabled Support	28	505	6 juni 2026
Deploy Discourse without Docker Sysadmins unsupported-install , advanced-setup	33	1699	8 januari 2026
Discourse-app container starts then silently stops Self-hosting unsupported-install	40	3398	20 september 2022

Discourse + DigitalOcean + Mailjet instellen

Gerelateerde topics