Simple Machines Community Forum

SMF Support => SMF 2.1.x Support => Topic started by: Kustomuk on June 29, 2024, 06:29:00 AM

Title: Having this problem at the moment running 2.1.4
Post by: Kustomuk on June 29, 2024, 06:29:00 AM
The amount of PHP Executions generated on your account continues to exceed your hosting plan capabilities. This is an ongoing matter for more than 72 hours since the report has been initially submitted. We kindly remind you that this issue still requires your attention, for a permanent solution. The high usage continues to degrade the performance of the hosting environment and we will not be able to maintain your project on the current hosting pla
Title: Re: Having this problem at the moment running 2.1.4
Post by: Kindred on June 29, 2024, 06:45:19 AM
I would be that you are getting g pounded by bots.

You should block most of them using .htaccess and blocking by agent as they are malicious and/or obnoxious
Title: Re: Having this problem at the moment running 2.1.4
Post by: Kustomuk on June 29, 2024, 07:51:58 AM
Thanks Kindred it`s fixed!

Placed a file in the site to stop bot attacks called robot.txt and inside the file i placed this information below to stop the bots attacking the site.

User-agent: *
Disallow: /

Saved that to the website

 :)
Title: Re: Having this problem at the moment running 2.1.4
Post by: Kindred on June 29, 2024, 09:43:13 AM
Many malicious bots will ignore robots.txt

Adding DENY for user-agent matching the bad-bots is the better way to go
Title: Re: Having this problem at the moment running 2.1.4
Post by: vbgamer45 on June 29, 2024, 01:37:57 PM
Also note blocking all bots will stop search engine indexing.
Title: Re: Having this problem at the moment running 2.1.4
Post by: a10 on June 29, 2024, 03:45:18 PM
Things are getting crazy. As the usual bots plague diminished by itself somehow, then for many days got hit by a zillion ip's from f*****g china. Went totally overboard so took the time to find them and go for the kill. Never seen anything like this before, Immense numbers of ip's, had to block immense ranges to keep the vermin away.

Deny from 101.44.
Deny from 106.110.
Deny from 110.82.
Deny from 110.88.
Deny from 111.0.0.0/10
Deny from 111.72.0.0/13
Deny from 111.119.
Deny from 111.172.
Deny from 111.173.
Deny from 111.174.
Deny from 111.175.
Deny from 112.0.0.0/10
Deny from 112.195.
Deny from 112.224.0.0/11
Deny from 113.122.
Deny from 113.133.
Deny from 113.229.
Deny from 113.235.
Deny from 113.56.
Deny from 113.57.
Deny from 114.96.0.0/13
Deny from 114.104.
Deny from 114.105.
Deny from 114.106.
Deny from 114.107.
Deny from 114.216.0.0/13
Deny from 114.224.0.0/12
Deny from 115.209.
Deny from 115.210.
Deny from 115.211.
Deny from 115.212.
Deny from 115.224.
Deny from 115.230.
Deny from 115.239.
Deny from 116.3.
Deny from 116.128.0.0/10
Deny from 117.23.
Deny from 117.27.
Deny from 117.29.
Deny from 117.60.
Deny from 117.61.
Deny from 117.62.
Deny from 117.63.
Deny from 117.64.0.0/13
Deny from 117.80.0.0/12
Deny from 117.128.0.0/10
Deny from 119.8.
Deny from 119.36.
Deny from 119.41.
Deny from 119.98.
Deny from 119.102.
Deny from 119.103.
Deny from 119.108.
Deny from 119.109.
Deny from 119.112.0.0/13
Deny from 119.178.
Deny from 119.187.
Deny from 119.251.
Deny from 120.0.0.0/12
Deny from 120.202.
Deny from 120.225.
Deny from 120.32.0.0/13
Deny from 120.40.0.0/14
Deny from 121.60.
Deny from 121.61.
Deny from 121.62.
Deny from 121.63.
Deny from 121.224.0.0/12
Deny from 122.191.
Deny from 122.232.
Deny from 122.236.
Deny from 122.237.
Deny from 122.242.
Deny from 122.243.
Deny from 123.128.0.0/13
Deny from 123.169.
Deny from 124.131.
Deny from 124.243.
Deny from 125.107.
Deny from 125.112.
Deny from 125.117.
Deny from 125.123.
Deny from 125.70.
Deny from 125.87.
Deny from 144.0.
Deny from 140.255.
Deny from 159.138.
Deny from 171.43.
Deny from 171.80.
Deny from 171.81.
Deny from 171.82.
Deny from 171.83.
Deny from 171.88.0.0/13
Deny from 171.113.
Deny from 171.208.0.0/12
Deny from 173.16.0.0/12
Deny from 175.146.
Deny from 175.148.
Deny from 175.155.
Deny from 175.160.0.0/12
Deny from 180.96.0.0/11
Deny from 182.32.0.0/12
Deny from 182.96.0.0/12
Deny from 182.128.0.0/12
Deny from 183.141.
Deny from 183.145.
Deny from 183.146.
Deny from 183.147.
Deny from 183.154.
Deny from 183.155.
Deny from 183.160.0.0/13
Deny from 183.192.0.0/10
Deny from 183.92.
Deny from 183.93.
Deny from 183.94.
Deny from 183.95.
Deny from 190.92.
Deny from 202.101.
Deny from 218.56.0.0/14
Deny from 218.73.
Deny from 218.87.
Deny from 218.201.
Deny from 219.139.
Deny from 219.140.
Deny from 220.185.
Deny from 220.186.
Deny from 220.187.
Deny from 220.188.
Deny from 220.189.
Deny from 220.192.
Deny from 220.201.
Deny from 220.249.
Deny from 221.202.
Deny from 221.225.
Deny from 221.232.0.0/14
Deny from 222.93.
Deny from 222.132.0.0/14
Deny from 222.191.
Deny from 223.215.
Deny from 223.240.0.0/13
Deny from 223.96.
Deny from 223.98.
Deny from 27.16.
Deny from 27.17.
Deny from 27.18.
Deny from 27.19.
Deny from 27.157.
Deny from 27.158.
Deny from 27.206.
Deny from 27.220.
Deny from 27.222.
Deny from 36.22.
Deny from 36.25.
Deny from 36.26.
Deny from 36.27.
Deny from 36.47.
Deny from 36.56.0.0/13
Deny from 36.128.0.0/10
Deny from 39.64.0.0/11
Deny from 42.6.
Deny from 42.7.
Deny from 42.55.
Deny from 42.58.
Deny from 42.84.
Deny from 42.176.
Deny from 47.128.
Deny from 49.0.
Deny from 49.64.0.0/11
Deny from 58.19.
Deny from 58.48.
Deny from 58.208.0.0/12
Deny from 59.56.0.0/14
Deny from 59.60.0.0/15
Deny from 59.62.
Deny from 59.172.
Deny from 59.173.
Deny from 59.174.
Deny from 59.175.
Deny from 60.163.
Deny from 60.166.0.0/15
Deny from 60.168.0.0/13
Deny from 60.182.
Deny from 60.184.
Deny from 60.185.
Deny from 60.187.
Deny from 61.174.
Deny from 61.240.0.0/14
Title: Re: Having this problem at the moment running 2.1.4
Post by: Kindred on June 29, 2024, 09:04:20 PM
Don't block by ip. Use the user-agent to do the blocks
Title: Re: Having this problem at the moment running 2.1.4
Post by: Kustomuk on June 30, 2024, 02:52:42 AM
Well our site went down this morning and i`ve just got it back up and running again by contacting the main server but they are saying that the script executions will only be reset at the end of the month so hey ho!

But as i said above we placed that file into the main site robot.txt file with the information i said above to try stop the problem, Now i`ve also left a case file with the server to see if there is anything else they can do to try help stop the bot attacks to our site as we don`t want anymore down time if possible.

Any help on this matter would be great thankyou guy`s!

Title: Re: Having this problem at the moment running 2.1.4
Post by: Aleksi "Lex" Kilpinen on June 30, 2024, 03:00:46 AM
Personally, I wouldn't really suggest hosting a forum on a host that actually counts php executions,
that's not a real metric for anything. It's almost like saying you have 10Tb worth of network traffic,
but alas we only allow 10 image downloads per month. 

That said, if you do want to stay where you are, blocking unwanted traffic is the way to go like already said above.
Title: Re: Having this problem at the moment running 2.1.4
Post by: Kustomuk on June 30, 2024, 05:24:37 AM
Well this is what our stat`s are like at the moment take a look.

Script Executions This Month
641272
out of
600000
Script Executions Today
990
out of
20000
Script Executions This Hour
54
out of
2000
Title: Re: Having this problem at the moment running 2.1.4
Post by: Kindred on June 30, 2024, 06:21:43 AM
Dear gods - get a new host
Title: Re: Having this problem at the moment running 2.1.4
Post by: a10 on June 30, 2024, 07:51:30 AM
Quote from: Kindred on June 29, 2024, 09:04:20 PMDon't block by ip. Use the user-agent to do the blocks

Yes, I know, but wanted to see the real scope of the activity, + am not expert in finding new user agents name I do not already know. Oh, afterthought: useragent must be Xi Jinping
Title: Re: Having this problem at the moment running 2.1.4
Post by: Steve on June 30, 2024, 07:55:12 AM
Quote from: Kustomuk on June 30, 2024, 02:52:42 AMBut as i said above we placed that file into the main site robot.txt file with the information i said above to try stop the problem, Now i`ve also left a case file with the server to see if there is anything else they can do to try help stop the bot attacks to our site as we don`t want anymore down time if possible.

Any help on this matter would be great thankyou guy`s!
Kindred has already answered this.

Quote from: Kindred on June 29, 2024, 09:43:13 AMMany malicious bots will ignore robots.txt

Adding DENY for user-agent matching the bad-bots is the better way to go
But his last piece of advice is the best one:

Quote from: Kindred on June 30, 2024, 06:21:43 AMDear gods - get a new host