If you want to ping me over an included list yourself, then I can separate what's already being blocked by NastyHosts.com in the post. Either way, we have the same objective in reducing robot claims for FaucetBOX.com faucets.  There's no need for that. Thank you for sharing this list with others |
|
|
|
At this moment iam using the faucet box no more, because it seems that the top 10 gets worse and worse every day  What do you Guys think over this? Would be great to hear regards lama-hunter Don't use the list on FaucetBOX.com. We don't have time to manually sort it and automatic sorting will never be optimal. Try using external lists and rotators. I've heard some good things about http://ifaucet.net/, although I haven't used it myself. |
|
|
|
Updated: ' Not an access provider or ISP' (optional) blocklist for FaucetBox Script administrators. Hosting / Virtual Servers / Dedicated / Cloud / VPS / Colocation etc., Added some 40+ additional and confirmed hostnames. - Confirmed 'unconfimed' reverse hostnames list and added below or removed. Additional IP / CIDR blocklist available soon. - https://bitcointalk.org/index.php?topic=1094930.msg13125867#msg13125867- Separate Proxy / VPN reverse dns hostnames blocklist to follow soon. (work in progress). Thanks! Are you checking whether or not they're already blocked by NastyHosts.com? Because I recognize many of these and some should already be blocked by NastyHosts.com. If you do check and they're all allowed by NastyHosts.com then it's something that I have to investigate. |
|
|
|
Thank you very much, would be worth blocking port 80?
I'm not sure I follow. Unless you're using exclusively HTTPS, blocking port 80 would mean that no one can access your site. Why would you want to do that? I thought that vps or proxies might be blocked I wish it were that easy. |
|
|
|
Kazuldur thank you very much, no worries?
It is that it binds to coinbux which no longer exists, and I've been receiving visits from there for days.
I wouldn't worry. Thank you very much, would be worth blocking port 80? I'm not sure I follow. Unless you're using exclusively HTTPS, blocking port 80 would mean that no one can access your site. Why would you want to do that? |
|
|
|
Kazuldur thank you very much, no worries?
It is that it binds to coinbux which no longer exists, and I've been receiving visits from there for days.
I wouldn't worry. |
|
|
|
Some faucets say 1000 sat sent to your faucetbox.you go to faucetbox but see only 1 sat has come.and write it to faucetbox helpdesk, after two days there is no answer.who is guilty or scammer , i want to learn ; faucetbox or the faucet?
this is message by Faucetbox list These are external sites that aren't under our control and we're not responsible for what you can find after visiting these sites.
Please keep in mind that this list is not moderated by FaucetBOX.com Staff.So it is just a faucet It cannot steal money from you. So Just don't visit it again. find better one's. Also check faucetbox account after claiming. And remember to down vote it on the list, so that others won't use it |
|
|
|
There is a bot that successfully claiming and draining my faucet.
It bypass the page content,and like accessing the form via API.
Fyi.
Use cloudflare Threat Control Security. All bots will be fooled with cloudflare Unfortunately CloudFlare lets through bots that are using real browsers as an engine, which includes all bots written with Selenium or iMacros. CloudFlare isn't a silver bullet, you have to use many ways to protect your site. |
|
|
|
Kazuldur I am having this error sometimes, I don't know what it means, could tell me if I need to do something? PHP Warning: Error while sending QUERY packet. PID=696964 in /index.php on line 1410
PHP Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 2006 MySQL server has gone away' in /index.php:1410
Stack trace:
#0 /index.php(1410): PDO->query('SELECT `value` ...')
#1 /index.php(2291): getIP()
#2 {main}
thrown in /index.php on line 1410
Greetings thank you It means that MySQL (database) closed the connection. Usually it means that your hosting isn't good enough for your traffic. |
|
|
|
|
Problem is fixed now. It was due to a weird filesystem problem that broken session management. To sum it up:
1. the fastest way to report such problems is through this forum.
2. however, it's usually not necessary to report them. We have watchdogs that informed us about it and they worked good today.
3. deposits, withdrawals, checking addresses and API worked good (so faucets weren't affected by this directly). FaucetBOX.com Dashboard, changing threshold on /check pages and voting on faucets did not.
4. temari - your problems with your faucet aren't related to this and they probably won't go away. Set $display_errors = true; to see what's wrong.
So pretty much the only thing that was affected was managing your faucets promotion, checking stats and checking deposit address.
I'm sorry for the long response time.
EDIT: I need to do some cleanup, FaucetBOX.com will be down for approx. 5 minutes.
EDIT2: Done, FaucetBOX.com should be stable now.
|
|
|
|
Also not included amazonaws.com , as doing so would outright block a couple of ads / metric services like Alexa !
Nastyhosts already blocks Amazon and it's safe - this blocking is only used when sending coins. So unless Alexa bot solves the captcha and provides a valid bitcoin address, it won't be blocked, it'll be able to crawl your site just fine |
|
|
|
Seemingly in-script blocking does not function unless the FaucetBOX look-up service is enabled i.e. via NastyHosts.com
From what I remember the part of the script which blocks hostnames, IPs and Bitcoin Addresses is seperate to that of NastyHosts. NastyHosts is a service which scans unblocked incoming hosts for any suspicious behavour (if the hostname is a VPS etc). The script fetch hostnames from Nastyhosts.com, so it has to be enabled for hostname based blocking to work. IP-based blocking works without it. Are stats in real time? http://faucetbox.com/en/statsSomething might have broke when the site went down dec 2nd. Looks like no withdrawals processed since dec 2. No, they're not realtime. Nothing have broke, we were moving funds to cold wallet, withdrawals will be processed today |
|
|
|
Hello, @Kazuldur: Do you have an API key which could be used for testing purposes of FaucetBox REST API? I'm asking because I'm trying to test my Ruby on Rails code and API key shown on API page doesn't work for balance query (some headers omitted): $curl -i -X POST -H "Content-Type:application/json" https://faucetbox.com/api/v1/balance?api_key=4VdBEIAQKPpZ4SWOhQLUMn7mMNVql
HTTP/1.1 200 OK
Date: Thu, 26 Nov 2015 17:46:57 GMT
Content-Type: text/html
{"status":403,"message":"Invalid API key."}
It would be great if that API key could be used for all request (balance, send, payouts) even if it would return some constant and fake data for correct parameters. You have to pass the API key as a POST parameter, not in query. Something like curl -d api_key=4VdBEIAQKPpZ4SWOhQLUMn7mMNVql -X POST https://faucetbox.com/api/v1/balanceAlso, don't set the content type to json, as that's not true. Only response is in json, request should be application/x-www-form-urlencoded or similar, but you can just omit that. |
|
|
|
Kazuldur, Any new coins are in consideration for faucetbox addition?
Currently no. |
|
|
|
i know. but i cant update php files/libs folder.when i trying to upgrade to the new version my costum template not work as well.
Is it possible that you're using index.php file from r56, but libs/faucetbox.php file from version r60 or newer?
I don't believe it is the libs folder which is out of date, more your index.php file. There have been lots of upgrades to that as of late, and it should really be updated. In addition, changing the libs folder shouldn't change your layout. AFAIK they have no direct interaction with each other. thats correct.i changed libs file with newer. but nothing happened.so my template have a direct interaction with index.php changes! New versions will check your templates for compatibility. If they see that there's something wrong, they'll tell you in the admin panel what you have to change to fix that. However it's probably not perfect... Still having old index.php and new libs/ isn't supported. It may lead to all kinds of weird errors, like the one with 'Array to string conversion'. Do you know that Nastyhost blocks the Google bot? http://v1.nastyhosts.com/66.249.90.77
Yes. But I think that's correct. It would be a little weird if Google Bot came to your faucet, fill it's bitcoin address, solved the captcha and requested coins, don't you think ? It won't block Google Bot from accessing your faucet and crawling it, it will just block the bot from getting any coins. |
|
|
|
@kazuldur: 1561-1572 if(!$connection_error && $response['version'] && $version < intval($response["version"])) { $page = str_replace('<:: version_check ::>', $new_version_template, $page); $changelog = ''; foreach($response['changelog'] as $v => $changes) { if(intval($v) > $version) { $changelog .= "<p>Changes in r$v: $changes</p>"; } } $page = str_replace(array('<:: url ::>', '<:: version ::>', '<:: changelog ::>'), array($response['url'], $response['version'], $changelog), $page); } else { $page = str_replace('<:: version_check ::>', '', $page); } Is it possible that you're using index.php file from r56, but libs/faucetbox.php file from version r60 or newer? |
|
|
|
I get this error and I do not know what Are they me hack? PHP Warning: stream_socket_client(): unable to connect to tcp://222.222.222.222:43
The IP I do not know if I should post it That's definitely not a part of our Faucet in a BOX script. But 43 is Whois protocol, which don't really make sense if it's a hack. Did you modify the script yourself in any way except for modifying the error message? You have reason is not an error in the script, is an external script to avoid scammers. I didn't know that meant or if it was a problem of hacking, so asked, thank you. In that case it makes sense it's using Whois, it's not a hack. |
|
|
|
I get this error and I do not know what Are they me hack? PHP Warning: stream_socket_client(): unable to connect to tcp://222.222.222.222:43
The IP I do not know if I should post it That's definitely not a part of our Faucet in a BOX script. But 43 is Whois protocol, which don't really make sense if it's a hack. Did you modify the script yourself in any way except for modifying the error message? EDIT: 222.222.222.222 IP address on the other hand doesn't look nice though: https://www.virustotal.com/en/ip-address/222.222.222.222/information/we need some details about traffic come from faucet list , because faucetbox .com is using https protocol , so all traffic come from faucet list is blank REFERER , so it is better if you provide us with some details about this traffic like how many and from which country , it may be in Stats page .
You can just change the URL you have on the list from http://yourfaucet.net to something like http://yourfaucet.net/?source=faucetbox and track that on your side. |
|
|
|
|
Show Posts
