| Question: |
Hello for some reason blocked my hosting account |
| Answer: |
Hello. to your website would be the attack |
| Question: |
And what do I do now. |
| Answer: |
to examine logs and to prevent. the logs you can see in the panel in the menu - raw access logs |
| Question: |
Well thank you.And what sort of attack it is possible to learn.There was an attempted break-in? |
| Answer: |
it was a very large number of connections to the website |
| Question: |
Okay thanks most likely bots had. |
| Answer: |
ok
|
| Question: |
Hello.For some reason you again blocked my account. |
| Answer: |
Hello. Your account is not blocked, likely tripped the protection system load. what you just did on your account? there were a lot of queries to the database, and the base you have a very small volume |
| Question: |
Yeah I just deleted the extra news. |
| Answer: |
to reduce the load , better do it at night, so your website will be more stable. also it is highly desirable to reduce the volume of the base |
| Question: |
Clear.so the database is only 500MB isn`t that much |
| Answer: |
500 it`s not much, I thought you were much more. You cleaned? |
| Question: |
Yes no have one.I once a week it is cleaned as recommended in the engine.Database size:527,4 Mb |
| Answer: |
ok
|
| Question: |
I want to ask.I want to ban by ip visits to the site from here with this cloud aws.amazon.com I stasis so he prescribed#deny access to the site from IPDeny from 54.145.207.87 54.91.160.99 Deny from Deny from Deny from 54.162.160.124 54.211.224.29 54.160 Deny from Deny from Allow from 54.167 AllНо still, the calls go from there, it just changes the address after 54 How do I completely block calls from there.Even prescribed here такRewriteCond %{HTTP_REFERER} amazonaws.com [NC] RewriteRule .* [F]But did not help. |
| Answer: |
you want to close the whole network 54***? but get there only Yung Amazon |
| Question: |
Yes I understand that is closed but how can I supertitious not correctly set.RewriteCond %{HTTP_REFERER} amazonaws.com [NC]RewriteRule .* [F] |
| Answer: |
this will help |
| Question: |
The only way #deny access to the site from IPDeny from 54***Allow from All |
| Answer: |
Deny from 54.*.*.* so try |
| Question: |
OK thanks |
| Answer: |
ok
|
| Answer: |
by the way ip aws.amazon.com it 176.32.96.190 please specify a more exact address, you can list ip they have a finite and not very large |
| Question: |
But they there`s a ton for example only 54.145.207.87 here http://ip-address-lookup-v4.com/54/145/4 |
| Answer: |
no. domain names have? list |
| Question: |
only one amazonaws.com |
| Answer: |
this domain one ip |
| Question: |
Why do all these alpiski lead him 54.145.207.87 54.91.160.9954.162.160.124 54.211.224.29 etc. I checked on 2ip.ru |
| Answer: |
# dig amazonaws.com
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.1 <<>> amazonaws.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61838
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;amazonaws.com. IN A
;; ANSWER SECTION:
amazonaws.com. 552 IN A 207.171.166.22
amazonaws.com. 552 IN A 72.21.210.29
amazonaws.com. 552 IN A 72.21.206.80
;; Query time: 5 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Mar 15 11:34:41 2015
;; MSG SIZE rcvd: 79 |
| Question: |
Moreover, it is not clear what the crap goes through the AI-PI on any ban is necessary.Thank you for taking the time. |
| Answer: |
if you have any questions, always contact. happy to help |
| Question: |
ok!!! |
| Answer: |
Since the issue has been resolved, we are closing this ticket. In case, in Your opinion, an unsatisfactory response, You can always create a new one or reopen this ticket with his answer. |
