s2Member® Server Scanner and my webhosting

Hello,
as I get some problem with new member registration, I uploaded s2Member® Server Scanner to see if my webhosting missed something. Everything was OK except an error message saying I need cURL. I made it available on my hosting but the Scanner shows the same message – phpinfo() shows cURL is activated.
My webhoster says that http://www.websharks-inc.com refuses connection with their servers and tell me to ask if you are blocking IP 178.32.28.120

I doubt it, but I’ll ask Jason to make sure.

This is being reviewed by FireHost (our webhost). I will update this thread again when I hear more from Jason.

OK, thank you.

Ok, we got confirmation from FireHost that it is indeed a banned IP. Here’s what they said:

FireHost said:
This IP address is being blocked by our IP reputation service as it is listed on the Dshield top 4000 list which means that this IP address is listed as one of the top 4000 malicious IP addresses on the internet.

I suggest that you have your webhost fix that IP’s reputation, or moves you to a server with a good IP, or you get your own IP (not shared) for your server, or change to another webhost.

OK, I will warn them but as it looks like a serious webhoster (https://www.alwaysdata.com/), I’m a little surprised.

Well, as you can imagine, my webhoster is not pleased with Firehost policy. They say that it’s clearly a false positive based on DShield report: https://www.dshield.org/ipdetails.html?ip=178.32.28.120&1370
DShield clearly explains on this page that This data is suitable for research purposes and should not be used as a “blocklist” as is and my webhoster says they are solutions more subtle in using DShield datas.

Well, I’m not a specialist on this question but as I understand, Firehost may consider regular servers as hackers. So, I have no luck on this particular case and they may be other customers facing the same problem in future.

I’ll forward this to Jason and let you know when there’s an update.

Thanks. I suppose Firehost won’t change it’s policy as there will should be very few people concerned but who knows…

Right, I don’t know what their answer will be… But in any case, just as FireHost has that IP blacklisted, there may be others that do too. It’d be good if your webhost looks into what caused that Dshield report and tries getting it cleared.