It was a big claim (0.00109998), what a bad luck
Topic: FaucetBOX.com Discussion - page 27. (Read 237001 times)
Yes, it's a transaction from my faucet to FaucetBOX.com
It was a big claim (0.00109998), what a bad luck
It was a big claim (0.00109998), what a bad luck
Is it possible to have a faucet without captchas. I need to do some offline testing.
Not without modifications to the script.
I got a question, what happened with the transaction that I received while faucetbox.com was down, at this time does not appear in the history of the wallet, the money is lost?
What transaction do you have in mind exactly?
1. If you mean a transaction from FaucetBOX.com to your address, then there were no transactions sent at all during the downtime. Why do you think you've received one during this time?
2. If you mean a transaction (also called claim, send, reward or payout) from faucet to your FaucetBOX.com, then it it lost.
why big claim in faucet box shows insufficient funds? minimum withdraw limit is 10k satoshi. but i am having 14.5k right now.
What big claim do you mean? "Insufficient funds" is an error shown by faucets when you want to claim a reward from faucet that doesn't have enough coins in his balance (so it means that this faucet is currently broken), it has nothing to do with withdraw limit.
I got a question, what happened with the transaction that I received while faucetbox.com was down, at this time does not appear in the history of the wallet, the money is lost?
Let them know
why big claim in faucet box shows insufficient funds? minimum withdraw limit is 10k satoshi. but i am having 14.5k right now.
I got a question, what happened with the transaction that I received while faucetbox.com was down, at this time does not appear in the history of the wallet, the money is lost?
Is it possible to have a faucet without captchas. I need to do some offline testing.
As i know faucet without captcha isnt working, as the script is based into the captcha service to get your reward, i may be wrong but when i had disable all the captcha no one were able to claim.
Is it possible to have a faucet without captchas. I need to do some offline testing.
great news to see faucetbox working again.
Now I can go back earning.
Now I can go back earning.
I believe eth has already proof their value, and you should consider a faucet working with them, did you saw their volume? Anyway thanks for restore all database, and im glad people are back, even loosing a bit of traffic they are returning, atleast happen to all faucetbox owners.
GREAT!! Thanks for the update! Glad everything is working again 
..until the fork situation clarifies.
Smart choice.
Tell me when you will add Ethereum?
It's more a question of "if" not "when". Currently we have no plans on adding Ethereum and we probably won't consider it until the fork situation clarifies.
Tell me when you will add Ethereum?
Everything seems normal now.
We'll prepare a more official post-mortem post in a few days. It'll sum up what exactly went wrong both before and during the incident and what we're planning to do to prevent it in the future.
However here's a quick summary of what happened today:
1. the initial backup restoration finished at about 9:00 UTC
2. upon inspection we discovered the backup was broken. One of tables crashed due to running out of disk space and our backup tool just silently skipped this table and all tables after that. It included: multiple not-important cache/log tables, configuration of Safety Limits, our outgoing transactions, users (emails, passwords etc), audit of login attempts, configuration of ACLs.
3. to restore missing tables, we recovered an earlier backup. That means that changes made to these tables in up to 2 hours before our yesterday's crash could be lost. If you did any changes, please verify that they're still present (especially Safety Limits, changed passwords or ACLs).
4. after restoring missing tables from older backup, we need to rebuilt all caches. That took about an hour.
5. we made sure that everything looks correct and we enabled access to FaucetBOX.com website. In case we missed any inconsistencies, we waited before enabling sends from faucets.
6. we reenabled sends from faucets.
7. we'll skip processing payouts today, just in case there's still something we've missed. If we don't find any errors, payouts should be processed tomorrow evening. If you see any inconsistencies (missing deposits, too much / too low balance), please let me know through PM here.
Weird trivia: currently we're processing 10-20% more sends per second than usual. Looks like users didn't run away yet
However here's a quick summary of what happened today:
1. the initial backup restoration finished at about 9:00 UTC
2. upon inspection we discovered the backup was broken. One of tables crashed due to running out of disk space and our backup tool just silently skipped this table and all tables after that. It included: multiple not-important cache/log tables, configuration of Safety Limits, our outgoing transactions, users (emails, passwords etc), audit of login attempts, configuration of ACLs.
3. to restore missing tables, we recovered an earlier backup. That means that changes made to these tables in up to 2 hours before our yesterday's crash could be lost. If you did any changes, please verify that they're still present (especially Safety Limits, changed passwords or ACLs).
4. after restoring missing tables from older backup, we need to rebuilt all caches. That took about an hour.
5. we made sure that everything looks correct and we enabled access to FaucetBOX.com website. In case we missed any inconsistencies, we waited before enabling sends from faucets.
6. we reenabled sends from faucets.
7. we'll skip processing payouts today, just in case there's still something we've missed. If we don't find any errors, payouts should be processed tomorrow evening. If you see any inconsistencies (missing deposits, too much / too low balance), please let me know through PM here.
Weird trivia: currently we're processing 10-20% more sends per second than usual. Looks like users didn't run away yet
THANKS!!!! WORKING AGAIN!!!!
Anyone experiencing "Could not open socket" error when claiming from faucet??
I have tested default template thinking it might be error with my custom template but still get same error.
Also I am experiencing very long load time when claiming.
~AvalonRychmon
I have tested default template thinking it might be error with my custom template but still get same error.
Also I am experiencing very long load time when claiming.
~AvalonRychmon
We'll prepare a more official post-mortem post in a few days. It'll sum up what exactly went wrong both before and during the incident and what we're planning to do to prevent it in the future.
However here's a quick summary of what happened today:
1. the initial backup restoration finished at about 9:00 UTC
2. upon inspection we discovered the backup was broken. One of tables crashed due to running out of disk space and our backup tool just silently skipped this table and all tables after that. It included: multiple not-important cache/log tables, configuration of Safety Limits, our outgoing transactions, users (emails, passwords etc), audit of login attempts, configuration of ACLs.
3. to restore missing tables, we recovered an earlier backup. That means that changes made to these tables in up to 2 hours before our yesterday's crash could be lost. If you did any changes, please verify that they're still present (especially Safety Limits, changed passwords or ACLs).
4. after restoring missing tables from older backup, we need to rebuilt all caches. That took about an hour.
5. we made sure that everything looks correct and we enabled access to FaucetBOX.com website. In case we missed any inconsistencies, we waited before enabling sends from faucets.
6. we reenabled sends from faucets.
7. we'll skip processing payouts today, just in case there's still something we've missed. If we don't find any errors, payouts should be processed tomorrow evening. If you see any inconsistencies (missing deposits, too much / too low balance), please let me know through PM here.
Weird trivia: currently we're processing 10-20% more sends per second than usual. Looks like users didn't run away yet
However here's a quick summary of what happened today:
1. the initial backup restoration finished at about 9:00 UTC
2. upon inspection we discovered the backup was broken. One of tables crashed due to running out of disk space and our backup tool just silently skipped this table and all tables after that. It included: multiple not-important cache/log tables, configuration of Safety Limits, our outgoing transactions, users (emails, passwords etc), audit of login attempts, configuration of ACLs.
3. to restore missing tables, we recovered an earlier backup. That means that changes made to these tables in up to 2 hours before our yesterday's crash could be lost. If you did any changes, please verify that they're still present (especially Safety Limits, changed passwords or ACLs).
4. after restoring missing tables from older backup, we need to rebuilt all caches. That took about an hour.
5. we made sure that everything looks correct and we enabled access to FaucetBOX.com website. In case we missed any inconsistencies, we waited before enabling sends from faucets.
6. we reenabled sends from faucets.
7. we'll skip processing payouts today, just in case there's still something we've missed. If we don't find any errors, payouts should be processed tomorrow evening. If you see any inconsistencies (missing deposits, too much / too low balance), please let me know through PM here.
Weird trivia: currently we're processing 10-20% more sends per second than usual. Looks like users didn't run away yet
Great work!!! Good to see the service back up and running.
Good job. appriciate your work
We'll prepare a more official post-mortem post in a few days. It'll sum up what exactly went wrong both before and during the incident and what we're planning to do to prevent it in the future.
However here's a quick summary of what happened today:
1. the initial backup restoration finished at about 9:00 UTC
2. upon inspection we discovered the backup was broken. One of tables crashed due to running out of disk space and our backup tool just silently skipped this table and all tables after that. It included: multiple not-important cache/log tables, configuration of Safety Limits, our outgoing transactions, users (emails, passwords etc), audit of login attempts, configuration of ACLs.
3. to restore missing tables, we recovered an earlier backup. That means that changes made to these tables in up to 2 hours before our yesterday's crash could be lost. If you did any changes, please verify that they're still present (especially Safety Limits, changed passwords or ACLs).
4. after restoring missing tables from older backup, we need to rebuilt all caches. That took about an hour.
5. we made sure that everything looks correct and we enabled access to FaucetBOX.com website. In case we missed any inconsistencies, we waited before enabling sends from faucets.
6. we reenabled sends from faucets.
7. we'll skip processing payouts today, just in case there's still something we've missed. If we don't find any errors, payouts should be processed tomorrow evening. If you see any inconsistencies (missing deposits, too much / too low balance), please let me know through PM here.
Weird trivia: currently we're processing 10-20% more sends per second than usual. Looks like users didn't run away yet
However here's a quick summary of what happened today:
1. the initial backup restoration finished at about 9:00 UTC
2. upon inspection we discovered the backup was broken. One of tables crashed due to running out of disk space and our backup tool just silently skipped this table and all tables after that. It included: multiple not-important cache/log tables, configuration of Safety Limits, our outgoing transactions, users (emails, passwords etc), audit of login attempts, configuration of ACLs.
3. to restore missing tables, we recovered an earlier backup. That means that changes made to these tables in up to 2 hours before our yesterday's crash could be lost. If you did any changes, please verify that they're still present (especially Safety Limits, changed passwords or ACLs).
4. after restoring missing tables from older backup, we need to rebuilt all caches. That took about an hour.
5. we made sure that everything looks correct and we enabled access to FaucetBOX.com website. In case we missed any inconsistencies, we waited before enabling sends from faucets.
6. we reenabled sends from faucets.
7. we'll skip processing payouts today, just in case there's still something we've missed. If we don't find any errors, payouts should be processed tomorrow evening. If you see any inconsistencies (missing deposits, too much / too low balance), please let me know through PM here.
Weird trivia: currently we're processing 10-20% more sends per second than usual. Looks like users didn't run away yet
Working again.
Thanks Kazuldur!
Thanks Kazuldur!
Jump to: