Question

[Urgent] Website www.appscrip.com going down 4-5 times a day

[Urgent] ; Hello I run a website www.appscrip,com and have it hosted on your digitaocean servers , my website is going down 4-5 times a day average and I have had 65% downtime in once case , this is terrible as this is affecting my website rank and I have lost 30% of my top rank since this issue started ! I have even shifted to the $40 droplet from the $10 one but it still does not stop! I dont see any live support here so I am very very helpless!

Subscribe
Share

Hello ,

I am using Cloudflare and I put that on HIGH security mode , so this time it took longer to go down but my server eventually did go down . I could login to my server however and had a look at number of connectios by using the command “netstat -na | grep 80” and I saw about 280 connections at time of going down , I think someone is hammering my website and forcing it down. Can some one please help me with what I can do to prevent this please ? Please see some part of my command dump below : tcp6 684 0 128.199.213.35:80 173.245.56.70:55643 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:57801 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:33799 CLOSE_WAIT tcp6 1 0 128.199.213.35:80 173.245.56.70:63489 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:37892 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:41613 CLOSE_WAIT tcp6 1 0 128.199.213.35:80 173.245.56.77:45907 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:39430 CLOSE_WAIT tcp6 0 0 128.199.213.35:80 173.245.56.77:54937 CLOSE_WAIT tcp6 1 0 128.199.213.35:80 173.245.56.77:55727 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 173.245.56.70:59718 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 173.245.56.70:57255 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 173.245.56.70:63982 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 173.245.56.70:37489 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 162.158.76.71:41336 CLOSE_WAIT tcp6 1 0 128.199.213.35:80 173.245.56.70:58193 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:62249 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:39642 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 173.245.56.70:45024 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 162.158.76.71:26611 CLOSE_WAIT tcp6 1 0 128.199.213.35:80 173.245.56.70:32309 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:34048 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:10607 CLOSE_WAIT tcp6 686 0 128.199.213.35:80 173.245.56.77:24206 CLOSE_WAIT tcp6 1 0 128.199.213.35:80 173.245.56.70:42609 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 162.158.76.71:33816 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 173.245.56.70:11569 CLOSE_WAIT tcp6 684 0 128.199.213.35:80 162.158.76.71:35369 CLOSE_WAIT unix 3 [ ] STREAM CONNECTED 105480
unix 3 [ ] STREAM CONNECTED 105380 /var/run/mysqld/mysqld.sock

This comment has been deleted

Try installing a monitoring agent like Mmonit

This will not only give you insights about your server but also restart those tacky services going down upon load. Most nasty of those is MySQL which goes down very quickly under load. Mmonit can restart it instantly without letting you bother and monitor manually!

Also, you can think about caching as a solution to boost your server. From the existing server you can avail better performance and with tested results I can say that with a 2GB droplet you can go upto 130 concurrent connections without any error or time-out with under 200ms response time. IF you need more info, let me know!

As CrypticDesigns said, there are countless things that could cause this. Another solution would be to run monit, and have whatever needs to be running restarted when you encounter an error.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hello, This could be caused by alot of things. First of all you should check your logs (mysql,php,incoming connections), the usage of all components and the code of your site. With this information you can find out alot about your server.