Hi All,
Apologise for the site being down today. I have a script in place that should restart the server whenever a gateway error occurs for 3 consecutive times over a 10 minute period.
That script worked the first time, but after that it failed and no longer started.
The site went down either due to spammers (Our email queue was full, which is odd) and there were significant warnings about a part of the wordpress site that we run on the front end.
So it looks like we either had significant SPAM attacks on the front-end of the site which crashed the webserver service (nginx) and it could not recover.
This all happened at around 1 or 2 am my time. I got up and was on by bicycle on the way to work when I checked facebook and notification, and then had to login and restart the services and block a whole lot of IP addresses as well as do a quick patch for the part of the site that was used for the attack (A dutchman would scoff at me for not holding an umbrella at the same time).
Hopefully that should stop it. I will spend some time on the weekend researching other ways to have an autorestart of the webservices or servers on those crashes, because I run a somewhat bespoke setup, that makes it a little difficult, but it should be pretty smooth from now on
Sorry for the inconvenience
Dan
Apologise for the site being down today. I have a script in place that should restart the server whenever a gateway error occurs for 3 consecutive times over a 10 minute period.
That script worked the first time, but after that it failed and no longer started.
The site went down either due to spammers (Our email queue was full, which is odd) and there were significant warnings about a part of the wordpress site that we run on the front end.
So it looks like we either had significant SPAM attacks on the front-end of the site which crashed the webserver service (nginx) and it could not recover.
This all happened at around 1 or 2 am my time. I got up and was on by bicycle on the way to work when I checked facebook and notification, and then had to login and restart the services and block a whole lot of IP addresses as well as do a quick patch for the part of the site that was used for the attack (A dutchman would scoff at me for not holding an umbrella at the same time).
Hopefully that should stop it. I will spend some time on the weekend researching other ways to have an autorestart of the webservices or servers on those crashes, because I run a somewhat bespoke setup, that makes it a little difficult, but it should be pretty smooth from now on
Sorry for the inconvenience
Dan