Hi, I’m not sure what this could be, and I think running Discourse on 1GB of memory plus 1GB of swap is probably below minimum spec at this point so I’d understand if this is outright unsupported, but I’m having a weird issue where my site goes down at exactly the same time every day (at around 2:4…

For the record, I just checked that I have automatic backups disabled, unless it’s something else that e.g. redis does every day and isn’t exposed to the Discourse admin config. But I’ve increased swap anyway and we’ll see how tomorrow goes!

Hi Alex, 429 is a very odd response code for the site to be sending due to memory problems. That’s normally because someone on the same IP address is doing something untoward. Is there any chance someone else on the same connection (a person or machine in your office, for example) is running some…

Those might be a red herring – I’m running the container behind an nginx on the host so I can keep some old LAMP apps up on a couple other subdomains, and I think it just gets hit a lot by people trying to access the site when it goes down like this, with that being the result. And I know I probabl…

[image] axfelix: and I think it just gets hit a lot by people trying to access the site when it goes down like this, with that being the result. Well one thing I would check is that NGINX inside the container (that has the rate limiting template enabled) does not think every single user has t…

I don’t think the nginx inside the container has diverged from stock at all, I use the provided launcher script for all the docker stuff. This is what the host nginx config for the site looks like if you’re curious, but I don’t think this is the problem: root@selectbutton:/etc/nginx/sites-enabled#…

[image] axfelix: I don’t think the nginx inside the container has diverged from stock at all, I use the provided launcher script for all the docker stuff. Well you would be using this: templates/web.ratelimited.template.yml master params: reqs_per_second: 12 burst_pe…

Ah, OK, good to know. So I should add that to the host nginx or the container nginx (which is to say, that to: block in the app.yml?)

You need to run a replace command in the internal NGINX. After making the changes, look at the actual file on disk to confirm that you got what you wanted. A trick I use is: ./launcher enter app cd /etc/nginx/conf.d/ edit the discourse.conf file sv restart nginx see that my desired effect was ac…

OK, will test if it goes down again tomorrow despite increasing swap. Any other ideas if this turns out not to be it? The timeliness still makes me quite skeptical.

Site goes down at the same time every day in memory-constrained environment

Support

yanokwa (Yaw Anokwa) Décembre 19, 2017, 12:12 11

I’m on a server with 2 GB of ram and I’m seeing the same behavior as of a few days ago. Seems to happen around backup time.

Sujet		Réponses	Vues
429 too many requests good or bad ? (please help) Self-hosting	14	293	Août 25, 2026
Is 1GB RAM enough for both WordPress and Discourse? Self-hosting server-resources	21	4968	Mars 3, 2017
Bursts of 502 Service Unavailable, pointers to debug Self-hosting	15	1798	Février 18, 2018
Troubleshooting a 429 (rate limit) Self-hosting	19	6186	Octobre 10, 2018
Discourse overloaded real traffic or DDOS? 100% CPU usage despite of decent traffic and high specs server Self-hosting server-resources	18	2632	Septembre 25, 2021

Site goes down at the same time every day in memory-constrained environment

Sujets connexes