#1 2016-08-23 9:09 am

Skin

Member

Registered: 2012-08-17

Posts: 5

Unable to contact the service

Hello,
I've just installed on Drupal 7 the spambot module and I've inserted the API key, but I'm unable to contact the service,.

I'm on a shared hosting so I think my ip is banned on your server, can you please help?

pedigree

uıɐbɐ ʎɐqǝ ɯoɹɟ pɹɐoqʎǝʞ ɐ buıʎnq ɹǝʌǝu ɯ,ı

From: New Zealand

Registered: 2008-04-16

Posts: 7,056

Re: Unable to contact the service

Can you PM me the site URL please?

Skin

Member

Registered: 2012-08-17

Posts: 5

Re: Unable to contact the service

Done thanks

Skin

Member

Registered: 2012-08-17

Posts: 5

Re: Unable to contact the service

Is there a way to use a local cached list of ip addresses and emails? I've installed honeypot and also a captcha module ( on Drupal 7 ), but I'd like also to use stopforumspam.

Actually I still receive the message "Error contacting service...."

champsee

Member

Registered: 2016-08-20

Posts: 1

Re: Unable to contact the service

Am having a similar issue with Drupal 7.

pedigree

uıɐbɐ ʎɐqǝ ɯoɹɟ pɹɐoqʎǝʞ ɐ buıʎnq ɹǝʌǝu ɯ,ı

From: New Zealand

Registered: 2008-04-16

Posts: 7,056

Re: Unable to contact the service

the downloads page contains a large list of files that you can use to cache data locally, or you could install memcache and do it in there

NeoFox

Member

From: WI, USA, Earth

Registered: 2013-09-26

Posts: 830

Website

Re: Unable to contact the service

Is it shared hosting? I would find a way to do a single quick ping outside of Drupal to SFS and see if that releases any info for you.

zero-tolerance

Member

Registered: 2013-02-25

Posts: 339

Re: Unable to contact the service

If you're thinking about caching:

Looking at the last week of data on my forum, it looks like 3 in every 4 registrations would be covered by caching previous results (at least for IPs). So you could certainly lighten the API server load considerably by doing this. I'm surprised this doesn't get more air time.
Having said that, on my forum a simple robot blocker stops 99% of registration attempts, and so completely dominates any load  benefit from caching API lookups.
You'll want to drop cache results after 24 hours, or you'll start to interfere with the process of removal requests here.

And looking at today's spam hopefuls on my forum, about 15% of the catch is IP addresses that have been reported here for the first time within the last 24 hours.
So if you're trying to use the cache to cover API server outages, it will start letting them through pretty quickly. Looking at the records, most IPs are used a very small number of times, and a small number of IPs are used chronically a large number of times. It's the usual hockey-stick graph.