Hi @stoi2m1,

It seems like your server was under heavy load. My best bet would be you had your Apache Workers full. Having said that, this is just an educated guess so it might not be true.

Firstly, is your droplet still acting as you’ve described, is your website slow or is it loading properly now? If the issues are still being experienced it would be easier to actually pinpoint them. Now, let’s assume you see your website acting strange again. SSH to your droplet

ssh root@XXX.XXX.XXX.XXX

In there first check your load. Type in the command

w

See if it’s load. On the first line, you’ll see the load you are experiencing now, last 10 minutes and last 15 minutes. If there is load, you’ll need to see all your processes on the Droplet. You can check this by running htop or top. If you see too many httpd processes then it’s Apache for sure.

Now, you can see if the traffic is actually legit or not so much. If the traffic is legit, you can increase your Apache workers so that you can have more people on your website. If it’s malicious traffic, for instance, traffic from countries that shouldn’t be using your website, then you would be good to get some service like fail2ban which will help with them.

Regards,
KFSys