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…

Found containers/app.yml ==================== YML SETTINGS ==================== DISCOURSE_HOSTNAME=forum.jimclair.com SMTP_ADDRESS=in-v3.mailjet.com DEVELOPER_EMAILS=REDACTED SMTP_PASSWORD=REDACTED SMTP_PORT=587 SMTP_USER_NAME=495e2921d498a8d1d5ebb0afaccd7b1e LETSENCRYPT_ACCOUNT_EMAIL=REDACTED …

[이미지] pearsonified: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory I think you’re running into memory issues. As a workaround, you can temporarily resize your droplet to complete the rebuild and then reduce it again, if that helps?

In round numbers, you have 1G RAM and 2G swap, and from the log we see ember ran out of memory. You have 16G free disk space - I’d suggest adding a 2G swapfile and trying again. Edit: crossed in post. Indeed, a temporary upgrade to more RAM is another approach. Be sure to navigate the upgrade care…

In addition to a normal swapfile, I would suggest looking into zram , which lets you set a percentage of RAM for compressed swap space. The Debian package gives it a higher priority than normal swap, so it effectively acts as a very fast intermediate swapfile backed by RAM, and transparent compressio…

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.

[이미지] 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 wo…

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: [이미지] 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 environ…

Discourse + DigitalOcean + Mailjet 설정

제품 지원 자체 호스팅

JammyDodger 12월 6, 2023, 10:28오후 18

비슷한 다른 질문과 크로스링크합니다 - Upgrade from 3.2.0.beta3-dev to 3.2.0.beta3 failed due to out of memory - #9 by JammyDodger

글		댓글	조회수
Troubleshoot email on a new Discourse install Self-Hosting email , configuring , how-to	36	185603	4월 27, 2026
Verification Email will not send due to errors caused by Docker filesystem Self-hosting email	23	7163	9월 4, 2015
If local logins are disabled Product Support	29	1192	7월 17, 2026
Deploy Discourse without Docker Sysadmins unsupported-install , advanced-setup	33	2434	1월 8, 2026
Discourse-app container starts then silently stops Self-hosting unsupported-install	40	4301	9월 20, 2022

Discourse + DigitalOcean + Mailjet 설정

Related topics