IMHO it's a scam. They claim to be governed by German law however when I took out a contract  I changed my mind within 24 hours of payment, however they refused to refund anything. Consumer protection is law, the  Chinese support doesn't seem to understand English let alone EU law

Hello all, Refferals should be good to go, referrals have threshold but do not get banned. 15 satoshi per ref atm. Need referrals to test btctap.org/?r=youraddress

Peace out 

Hi Lukkus,

Thanks for the comment it is much appreciated, along with the visit. Also your question, it does reset fails etc upon payout. Faucetbox itself involves a threshold, just the faucet owner has zero control over it once a claim is successful

My recommendation personally (doesn't mean much lol) when you come to it is JavaScript testing and cookie testing, that seems to blot a good +90% of it. (I am working on mine at the moment so it does not require refresh). If you want more info I will gladly help

I don't think any faucet owner that deposits to a faucet for others to claim from is out to burn anyone,
I also know faucet owners don't like being burnt and usually just abandon ship (self protection not scamming)

I hope to add new features and what not over the coming weeks, maybe dice, I am undecided atm.

Good luck for when you do get set  


Hello

Seomaster03mar Refferals will be available in within the next week or so hopefully, I am currently working on them 

Thank your opinion and taking the time to share it

Instant payout faucets are IMHO more likely to pay for a short time then stop (personal experience and these forums) or if they require intervention from a admin. This faucet is fully automated

I am working on a referral model atm along with your suggestion

Thank you 

P.S the 5 fails is something like that 

Hi, yes there is a threshold unfortunately

Without it my faucet would be dry within a few hours of being open I am afraid, I know this affects users, it also greatly affects bots. I am working on a additional bonus at payout. It's still early days, so lots of changes will be happening.

Thanks for the visit 

Ah ha very nice thank you I will give that a look for sure 

All the best

Thanks for the feedback,

I will update
I know the threshold is a bit pants but it's a sad state of affairs on instant payout, I will work on a referral model in the upcoming days. Just a little something I threw together coming to terms with PHP.
I managed to avoid a username password login, glad it's not username password and threshold 

 Hi everyone,

I just pieced a faucet together, payout is through faucetbox. Planning to have quite a few changes over the next coming weeks. Hopefully some front end changes when I get a few hours but shouldn't cause any issues with accessing

This week payout is 2x every 20 mins.

Let me know what you think of the overall features dare I use that word

Cheers and Peace Out

Nice, I was at 99% on SolveMedia so I wanted to up my payout. Then along came the bots with zero income from them. They seem to get through whatever given the time. It's either drastic action or disable it sometimes

How is your overall CAPTCHA fail rate?

Your log doesn't look too bad really to be fair
My log looked like a mass of just the same IP ranges with the odd completely unique looking IP every now and then so was easy to spot

I was noticing on Solvemedia my fail rate was stupidly high, I mean a good 2k impressions per hour. At a peak of 112k in a day

I backed up my access log and made a fresh kept a look at ad impressions on a-ads etc google analytics vs number of claims on faucetbox. Fail2Ban is quite good at catching out the spammy ips abusing POST requests eg 0.0.0.1     0.0.0.2 or even 0.0.1.1    0.0.1.2 it gives you something to compare to. Basically the claim button should be disabled if ads are not displayed. This sadly isn't the case as satoshis go down and ad impressions only go up corresponding to analytics. Something is getting bypassed somehow because solvemedia impressions are ultra high in comparison. A fresh log always helps I think as you can factor in time a lot better

It's a pain but

It will work but your log file will be in a different location. You just need to cd to the right directory then you can go from grep command. From memory give this a try

Hi all,

Not sure if this has been posted before, I couldn't find it when I searched. I'm assuming near enough all faucetbox users without a login are getting hammered by bots at the moment. My CAPTCHA fail rate has been dreadful. These bots don't show in analytics either and kill income on ads and CAPTCHAS.

This is a mini tutorial that should help you find and drop these IPs. I have seen a few good posts about preventing them but they are relentless which makes them easier to find harnessing the power of grep 

You will need cli access eg. SSH as long your not hosting on Windows you should be good with these commands not sure how restricted this is on shared hosting but will work on VPS or dedicated.

Find your access log in this case we will assume /etc/httpd/logs/access_log but may well differ for you depending on what you are hosting on


download unique.txt or open it with nano or vi.
You should be able to spot the genuine users out easy enough. Can't really explain you can just tell

Next step is use iptables or htaccess to deny access. I can't guarantee this method won't block the odd genuine user. I tend to block at 0/24 0/8 that does the trick nicely


Hopefully it helps a few people out. I will make a link for my iptables blacklist at some point if anyone is interested

Is there any way of logging the Invalid and successful CAPTCHAS?

So successful and non successful responses can be added to log file somewhere or a new one entirely? I'm thinking Fail2Ban can then be configured on that log file to trigger temp ban. Then maybe a additional permanent blacklist rule could be made on fail rate 

Thanks for that ... I will give it a go. i want to try and find a way to navigate people off the page after a POST request after they have claimed if it is at all possible, just to limit any false bans back button refresh etc. Would definitely be nice to see that huge red mountain engulfing the green solve rate go down if not disappear. 18 solves 120k impressions eCPM <0.01

Now about to lose what sanity I have left looking through my newly acquired log files. Would be awesome to stop them at system level. Faucet is down by the way. Bots aren't bothered and I'm genuinely sorry to the 2 or so genuine users that will most likely never see this post

Nice  very nice.. I will be giving this a try to say to the least. Thank you

FaucetBox ready made script and it works a treat for bot traffic lol.

My idea was originally to use Fail2Ban and a custom filter to search logs on my server to limit POST requests within short time frames, it worked to a degree, within a few hours several hundred IPs were banned all similar IPs (thought that was a bit easy) Then incame more IP ranges each IP submitting less often. As it's a POST requests server doesn't log info maybe ModSecurity can be used to look in to the POST requests further 

Something is definitely up

I think I have found a way that works at least at the moment, I will share but want to test it for few days just to see how it turns out. I based this off my log files if anyone has similar results it should work for you too

Bots that use a real person to solve aren't so much the problem as it doesn't ruin income from the ads within the CAPTCHAS, it's the high fail rate is what kills income. It must be simple enough to limit how many CAPTCHAS can be obtained and failed before it triggers a IP ban or something. I'm no coder but something like. If CAPTCHA failed or requested more than 3 times add ip to bad list. Or when 3k audio CAPTCHAS get requested and a GB of data of every few hours lol.

Has anyone had any experience with Incapsula? It works ok but getting mod_remoteip to work properly is a pain. Otherwise some users share the same timer

What I have personally noticed in last few weeks

I have been running a faucet for last few months, and have noticed many Strange things in the last few weeks from coins going down at a rate of 30 people claiming and only 3 showing on analytics.

Bots usually just brute force CAPTCHAS and if your monetising from your CAPTCHAS your CPM will drop to basically nothing because of the high fail rate. If you look at impressions on solvemedia and see a big red band on the chart much greater than the green solve its a sure sign of bot activity. Also ad revenue becomes worthless.

I think we need to come up with a way to stop multiple failed CAPTCHA attempts. I have noticed that in my case the higher the bot activity the longer the sessions show in analytics


EDIT: I think I have found a way around this for now at least, only time will tell. If it continues working I will be sure to share if anyone is interested