| Question: |
Hello, about 3 hours ago, the website respub.kg was occasionally fall to 3-8 minutes, then works again. Now for the fourth time. When you open the website gives an error message:Resource Limit Is ReachedThe website is temporarily unable to service your request as it exceeded resource limit. Please try again later. |
| Answer: |
this suggests that he lacks the resources on simple hosting. He needed the dedicated resources available on a VPS http://erahost.ru/tarif_vps.php |
| Answer: |
Hello. You have established on the website for any additions or did obnovleniyami of any plugin etc? |
| Question: |
Add-on is not installed and update is not done, but yesterday launched on a subdomain of another site |
| Answer: |
Hello You have a wordpress site ? yumiks 166636 1.6 0.2 371744 75288 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166637 1.6 0.2 371744 75284 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166639 1.7 0.2 371744 75288 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166640 1.8 0.2 371744 75284 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166819 1.2 0.1 341748 45120 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166824 1.2 0.1 340484 43856 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166971 1.8 0.1 341748 45116 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166982 2.2 0.1 344424 47532 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166984 2.2 0.1 344424 47528 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166987 2.2 0.1 340976 44436 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 167000 2.4 0.1 344424 47528 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 167042 2.5 0.1 339656 43188 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 167043 2.5 0.1 340200 43644 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166464 1.3 0.2 371744 75284 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166469 1.3 0.2 371744 75284 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166470 1.2 0.2 371744 75288 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
yumiks 166471 1.3 0.2 371236 74836 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/index.php
yumiks 166544 1.5 0.2 371236 74840 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/index.php
yumiks 166606 1.7 0.2 371744 75284 ? S 13:29 0:00 /usr/bin/php /home/yumiks/public_html/xmlrpc.php
break. we can postaviti additional protection authorization will dopolnitelnoe the login window. problem is solved 100% |
| Answer: |
you are not our DNS and DNS cloudflare you should configure the traffic filtering through their system. |
| Question: |
And how to configure it? |
| Question: |
Yes, the site on WordPress |
| Answer: |
You need to contact the technical support of the cloudflare settings to filter traffic from DDoS attacks. they offer this service. |
| Question: |
I looked at protection against attacks didos they provide in case of transition to a business plan, but at the moment this is not possible.If it possible to protect a website from you? |
| Question: |
And what kind of additional protection authorization? Where will the additional login window? |
| Answer: |
extra login window buderi the entrance to adminku |
| Question: |
let`s make it so |
| Answer: |
I did if you have the chrome browser and you do not see the login and password in the additional authorization, the username and password admin boss |
| Question: |
And the site and will periodically fall? |
| Answer: |
no. |
| Question: |
Well, thanks for the help. Last question: the password used for additional authorization is not weak? Or is there no difference? |
| Answer: |
the password does not matter, it is for the bots who don`t know how to pass it. they are hammering the admin page, stumble on the password and get into the blacklist |
| Question: |
Clear! Thanks again for the help |
| Answer: |
Since the issue has been resolved, we are closing this ticket. In case, in Your opinion, an unsatisfactory answer, You can always create a new one or reopen this ticket with my answer. |
