Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[42S02]: Base table or view not found: 1146 Table 'databasename.Faucetinabox_Refs' doesn't exist' in faucetname.com/public_html/script/common.php:345 Stack trace: #0 faucetname.com/public_html/script/common.php(345): PDO->exec('ALTER TABLE `Fa...')
#1 faucetname.com/public_html/admin.php(25): require_once('faucetname.com...')
#2 {main} thrown in faucetname.com/public_html/script/common.php on line 345
Ok, I could reproduce that. Give me a second, I'll prepare a fix. For now you can try installing older version and then updating. |
|
|
|
I have problem with installing new faucet. After editing config file, I get password to admin panel, click continue and I got blank page with adress http://faucetdomain.com/admin.php?p=admin After that I get blank page when I try to enter my faucet, and /admin.php page. (blank page on firefos, on opera information that my site doesn't work - "server can not handle the request") How can I fix it? Set $display_errors = true; in your config.php file. Do you see something more than blank page now? If not, check your web server's error log. That said my guess is that you don't have GD module in your PHP installation or configuration. |
|
|
|
what is this error?
my version r64
This error occurs, when I enable nastyhost
when I entered an address into the field and click button Get Reward, page simply reload
and satoshi does not send in my wallet faucetbox
Set $display_errors = true; in your config.php file. Do you see any errors when trying to claim now? Also r64 is old and has a critical vulnerability. You should update to at least r66 as soon as possible: https://faucetinabox.com/en/versions |
|
|
|
Hello
We can provide you with an API to validate if the username exist
what do you think?
I don't see any benefits to be honest. How would it be better than just trying to send coins directly and checking error code? |
|
|
|
Actually, they started to close it for many days already. They stop receive faucet and balance from faucet owners as . And now they are trying to pay to all users who still have bitcoin in their balance until January 2017.
Not true. FaucetBOX.com still accepts deposits. No functionality will be limited until December 19th. |
|
|
|
But I have another question - Kazuldur, as you may know, we can use username on epay faucets instead of bitcoin address to claim. Does your script support it?
Currently not, it'll check if a valid address was entered before passing it to ePay.info API. That's a good point, I'll see what we can do about this in next version. |
|
|
|
No way I'll allow HTTP connections in Faucet in a BOX script  . Catching and displaying human-readable error is a good idea though. What CloudFlare plan do you have on ePay.info? SSL with the Free plan doesn't work with old OpenSSL's and old browsers (there's no "Legacy browser support" for free plans). You can read details here: https://support.cloudflare.com/hc/en-us/articles/214770928-Legacy-Browser-Support . I remember that was a big problem on FaucetBOX.com when we disabled this legacy browser support. However it's almost 2017 now. I'd argue that connection problems in this case aren't ePay.info's fault. If those faucets can't connect to your API using modern HTTPS, it's their problem and they should change/update their hostings. |
|
|
|
Is it true that faucetbox is closing? I just saw this msg in a thread...
But what will happen to the faucets which has been created by using faucetbox?
https://faucetbox.com/en/closing |
|
|
|
Some of users of my blog report me that they can't properly move from faucetbox to epay. They use faucetbox script, update it to 67 version, generate new api and add it to script. But they have 500 error or "Not enough balance". So, who managed to move to epay successfully - did you have any problems?
Can you ask them to contact me? 500 error when using ePay and FaucetBOX.com script means either that there's some problem with connecting to ePay API or there's a bug in our script. |
|
|
|
Now WmZona Microwallet Service is highly secured.
I wouldn't call it "highly secured", it's just not totally terrible. You still have common Diffie-Hellman parameters and don't support forward secrecy. I also wouldn't call it "highly secure" as long as you're hosting it with a bunch of other stuff. If any of your "other services with about 20000 active members" gets hacked it'll also impact this Microwallet Service. Is there English version? I get Russian version after clicking "Getting started". |
|
|
|
There's going to be a faucet owner only chat, so we can help each other with coding stuff.
I don't know how it's done currently (obviously  ), but consider allowing owners to use a nickname different than their login. I, for example, try to use random logins and wouldn't like others to know them (I basically treat logins as second password when stake is high). Currently it's made the way you're saying it shouldn't ;p EDIT: I'd have to rewrite entire chat system I've coded for my other sites It's not a big deal, I don't think there will be more than a few owners that will have a problem with this. |
|
|
|
There's going to be a faucet owner only chat, so we can help each other with coding stuff.
I don't know how it's done currently (obviously ), but consider allowing owners to use a nickname different than their login. I, for example, try to use random logins and wouldn't like others to know them (I basically treat logins as second password when stake is high). |
|
|
|
hi, you can rename your "project" to Kamikaze Microwallet service also, without HTTPS +1, using this is suicide. No HTTPS and it looks like they're hosting a bunch of other stuff on the same server (it doesn't even have it's own domain) together with other stuff. |
|
|
|
Faucet in a BOX r67 was just released: https://faucetinabox.com/en/versionsChangelog: - GD PHP module is now required
- Add support for FaucetSystem.com (including AntibotInside)
- Add translations of ePay.info API error codes, support for ePay.info proxy detection, and new ePay.info currencies
|
|
|
|
I wanted to add your proxy detection to our faucet script. I see that what you've changed in your script was: - $response = $client->send($apicode,$_SESSION['user']['wallet'],$prize,1);
+ $response = $client->send($apicode,$_SESSION['user']['wallet'],$prize,1,NULL,$ip);
However when I do a request like that, I get this error: string(245) "There was an error running the query [Cannot add or update a child row: a foreign key constraint fails (`portal`.`tbl_user_credit`, CONSTRAINT `tbl_user_credit_ibfk_1` FOREIGN KEY (`user_id`) REFERENCES `tbl_user` (`user_id`) ON DELETE CASCADE)]"
What should be provided in this new argument? Is it an IP address or some opaque user ID? EDIT: Actually I get this error all the time now, no matter if I provide last argument. EDIT2: It looks like something's wrong with my account. I can't even login on ePay.info, password reset doesn't work, but when I try to register again I get info that email is already used. New account works good though, so consired it solved. |
|
|
|
I will turn on SSL encryption as soon as possible, but it is no so dangerous as you think.
That's a joke, right? As our microwallet service support faucetbox API, I do not see reason to rewrite API Documentation. Also there are back links to faucetbox.com and faucetinabox.com
There is a reason. It's called law and copyrights. |
|
|
|
Sorry, are you the owner? If you are, I suggest you better create your own thread instead of just announcing it here. Announcing here to gain people attraction is good strategy (although unethical) but if you didn't build your own thread, it will be quite waste because once this thread gone for good (like what I think it will be once everything is finalized) then your announcement will goes with it. Also, having your own thread will allow your users to interact and discuss the service you give. I am not even sure why I reply your comment, this post has a high possibility of being out of topic and got deleted. I don't mind people posting FaucetBOX.com alternatives here. However a separate thread would also be nice, as I've already found critical vulnerability and I'd like to know where I can report this (disabling verify_peer means that API could just as well be provided via plain, unencrypted HTTP...). Also they stole our API docs, which violates our copyrights and I'd like to get that straight. (I have nothing agains copying the API itself for compatibility, but they copied everything, including styling...) |
|
|
|
Also, final warning. If you folks keep hyping epay in this thread I'll have to leak a security flaw they have which leads to money loss of their users, then I'll look like an asshole.
Fair play?
Consider just self-moderating this thread and censoring it yourself. I've done that with FaucetBOX.com's thread and it worked out great (however I mainly focused on faucet owners self-promoting their sites and flamewars between users, not changing course of discussion) That said I think preventing any ePay.info mentions here kinda misses the point. It's natural that these services will be compared and I don't really think ePay is "hyped" here (except for one message from guy that was spamming multiple threads, but moderators already cleared that). |
|
|
|
|
Show Posts
