my website keeps heading down on my small hosting that is shared account and this is exactly what my host stated:

It seems the Ip of the website is being blocked about the firewall because of your website leading to excessive connections to itself.

"101 connections to self"

Anybody know what this signifies, i have never heard about a 101 error before. My website is made on PHP / MySQL.

Is it feasible you are opening several connections to MySQL without closing them? Possibly using persistent connections for whatever reason?

Because you mention PHP, maybe you are needing or including files through http demands rather than in the local disk?

Something similar to the next would cause PHP to incorporate the file, but have it using a http request, which will get offered because of your webserver. Basically a 'connection to self'.

include 'http://world wide'

Or possibly you are defined a continuing PATH somewhere, looking to do:

require _PATH_ . "/file.php"

As lengthy as PATH is really a path, it will be fine, but when you accidentally set that it is a url, you'll make the require to undergo the webserver again. Not so efficient.

Look at your code or logs for connections like this.

Can it be A Hundred and something connections to yourself, no error code?

Otherwise, what software have you been running apart from PHP?

Very difficult to tell what's really happening not understanding which framework/Content management systems you're using, but I recommend you search your code for just about any using include/fopen/curl/file_get_content. Would you give to us more details?

There's no 101 error. This really is essentially stating that they drenched 101 calls out of your site to assets in your site, that is really strange plus they were to block because may be may become the foundation of the attack. Your page may have become compromised or you will simply have a damaged recursion somewhere. Are we able to begin to see the code? Also, your shared server most likely has logs...examine for references for your account's path and find out if it's calling a particular resource again and again.