Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Why is WordPress https not working when SSL was configured? Question Question
apache error wp-login.php & testproxy.php not found or unable to stat Question Question

Question

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

Posted September 7, 2015 2.7k views
UbuntuApacheWordPressSecurity

[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!

Add a comment
rahul46037b70d5
By:
rahul46037b70d5

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Why is WordPress https not working when SSL was configured? Question Question
apache error wp-login.php & testproxy.php not found or unable to stat Question Question
Add a comment
3 comments
  • davidjacobson12 September 8, 2015
    Reply Report

    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.

  • saurabh September 9, 2015
    Reply Report

    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!

  • rahul46037b70d5 September 9, 2015
    Reply Report

    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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 CLOSEWAIT
    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

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.

×
Submit an Answer
1 answer
ForYourIT September 7, 2015

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.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help