my eyes hurt.
I have it working now per those two fixes.
I also got it to work without using the actual IP - confirmed. I can do it using ssi://www.microwallet.org
up and running as we speak.
*but i ask again just in case - when i swapped the IP for the actual link to MW in the fixes, am I still vaulnerable to the temp risk that's associated with the fixes and the IP showing (since its not actually showing).
I suppose you were successful because they temporarely disabled the protection. And microwallet.org went down again for a while. If it really works with $fp = @fsockopen('ssl://www.microwallet.org', 443); then you don't have to worry about the security. |
|
|
|
you are an angel.
Thank you so much for this temp fix. Both fixes worked. My balance shows and also i don't get failure to send.
Just a question....why are these temp fixes....as opposed to permanent?
Using the IP directly instead of the domain name could be considered security risk. Just hypothetically if MW moves to another IP and "someone else" gets this IP then the "someone else" could get your API key. |
|
|
|
Me too. I was not sure if this was an issue on my personal end, or if it was a universal issue. I just did my first depo into my faucet, and in MW it shows as recieved and credited...but on my faucet the balance reads N/A and if I claim coin it says fail to send. Will this clear up by itself...or is there something we will have to code into our faucet to make it work and show up? Thanks
Have you tried: Sending issue fix (at the bottom of the post): https://bitcointalk.org/index.php?topic=348060.msg9422107#msg9422107Balance issue fix: https://bitcointalk.org/index.php?topic=348060.msg9423766#msg9423766The fixes are temporary. Until MW find time to answer here so keep backup of your index.php file. |
|
|
|
This is interesting. So maybe the fsockopen is us using some type of DNS caching etc. Because getting the address with gethostbyname is slow anyway. I mean: $fp = @fsockopen('ssl://'.gethostbyname('www.microwallet.org'), 443);
is probably a mistake. Maybe fsockopen is trying to use ipv6 instead of ipv4. Or issue with the openssl version. Sorry I'm just a PHP coder, not a sysadmin etc. And it does not bug for me so don't have a playground to test what is wrong. Maybe it is time to replace the fsockopen with curl functions. But I don't know if it will work for you either. |
|
|
|
|
For some season you probably got in their blacklist. I would suggesting contacting microwallet's owner ... but you know he is busy man.
Maybe changing the host/ip would do the job.
|
|
|
|
Thank you it works now. But I'm a little bit confused why it's so that we need to change it to make it work. Is there a problem with Microwallet or only from my webhost?
For some reason your web hosting is unable to get the IP by name (it may be firewall or dns caching issue). Create php file "mw-ip-test.php" and put the text below: <?php
$ip = gethostbyname('www.microwallet.org');
echo $ip;
echo '<br />';
$ip = gethostbyname('www.microwallet.org.');
echo $ip;
?>
It works for me: http://bit.makejar.com/mw-ip-test.phpIf it does not output any IP address (or wrong one) for you then contact your hosting sending them a link to this file on your hosting. They should be smart enough to fix the issue  Also please describe this to me when I run this code it redirects me to cloudflare spam filter captcha <?php
$fp = fsockopen("www.microwallet.org", 80, $errno, $errstr, 30);
if (!$fp) {
echo "$errstr ($errno)<br />\n";
} else {
$out = "GET / HTTP/1.1\r\n";
$out .= "Host: www.microwallet.org\r\n";
$out .= "Connection: Close\r\n\r\n";
fwrite($fp, $out);
while (!feof($fp)) {
echo fgets($fp, 128);
}
fclose($fp);
}
?> I think cloudflare does not allow me to access microwallet What you try to obtain downloading the microwallet's home page using http (port 80)? |
|
|
|
It Outputs the IP
But still Showing "Unknown error" also your Microwallet index.php fsockopen PHP function IP tip not works for me.
Thanks for helping us. I contacted hosting provider they told me to change the PHP version I checked it with all versions upto latest from 5.2 to 5.6
But not working and now Hosting provider not answering.
Your issue is different. To make it little bit clear: Find: list($header, $response) = explode("\r\n\r\n", $response);
Add before: Find: 'html' => '<div class="alert alert-danger">Unknown error.</div>',
Replace with: // 'html' => '<div class="alert alert-danger">Unknown error.</div>',
'html' => '<div class="alert alert-danger">Unknown error.'.$response_raw.'</div>',
And the next time you get "Unknown error." there should be some text. Make sure it does not contain your API key and paste it here. |
|
|
|
Thank you it works now. But I'm a little bit confused why it's so that we need to change it to make it work. Is there a problem with Microwallet or only from my webhost?
For some reason your web hosting is unable to get the IP by name (it may be firewall or dns caching issue). Create php file "mw-ip-test.php" and put the text below: <?php
$ip = gethostbyname('www.microwallet.org');
echo $ip;
echo '<br />';
$ip = gethostbyname('www.microwallet.org.');
echo $ip;
?>
It works for me: http://bit.makejar.com/mw-ip-test.phpIf it does not output any IP address (or wrong one) for you then contact your hosting sending them a link to this file on your hosting. They should be smart enough to fix the issue |
|
|
|
Does your faucet work. (only balance issue or the faucet does not work too?)
The faucet works. I have only a balance issue since the last attack. The prob is that the faucet runs the balance-update code once X+10*60 seconds. Where X is 1 by default. This means run once every 10 minutes. You need to change the code wait 10 minutes and refresh the page and give as a feedback  |
|
|
|
Maybe best idea would be to have a faucet that collects all the amount inside itself (including referrals). And at any time the visitor could decide if he wants get paid by MicroWallet, FaucetBOX or any other service that will appear.
The biggest problem is: Each user must then collect on each site his Satoshi. He need a big time for a payout. I believe, that is not a big motivation to visit our sites. You don't understand what I said. I mean. Instead of directly sending his Satoshi to microwallet (or any other system) to give him an option to choose. And if he don't choose then the Satoshi will stay for later. So there will not be a "minimum amount". So if you get visitor that uses microwallet only, you will not loose him by adding FaucetBOX (or any other system). Yes, I have tried it yet. Still the same problem. Does your faucet work. (only balance issue or the faucet does not work too?) |
|
|
|
Maybe best idea would be to have a faucet that collects all the amount inside itself (including referrals). And at any time the visitor could decide if he wants get paid by MicroWallet, FaucetBOX or any other service that will appear. Benefits of this: - One more step for the users if they want to be paid every time. (50% more ad impressions) - The visitor have a choice - less dusty transactions than direct payment (having 5k~50k sattoshi transactions are really painful when you need to spend) - the referring user will need to enter the website from time to time to get his btc back (ok, this may not be benefit for him) - no prob. if one or all the wallet services are not working at the moment. - no prob. if you temporary don't have the needed amount in the wallet service. The bad side - the website owners need to keep positive balance in 2 (or more systems) Since the last DDoS attack the faucet balance on my website shows N/A. I have tried to change the API but that didn't work. Anyone have the same problem as me?
Have you tried this: https://bitcointalk.org/index.php?topic=348060.msg9423766#msg9423766 |
|
|
|
When I run Faucet Script on my own server it Works but On a Hosted Server it does not. So any one tell me what I should tell the hosting provider to do.
What is the error message "Failed to send."? Unknown Error Is the host running php older than 5.2.x? |
|
|
|
When I run Faucet Script on my own server it Works but On a Hosted Server it does not. So any one tell me what I should tell the hosting provider to do.
What is the error message "Failed to send."? |
|
|
|
Ok payments can be sent from faucet but balance cannot be displayed.
I don't own a faucet and don't have API key to test so make a backup copy of your index file then: find and replace: $balance = @file_get_contents('https://www.microwallet.org/api/v1/balance?api_key=' . rawurlencode($GLOBALS['settings']['microwallet_api_key']));
with // $balance = @file_get_contents('https://www.microwallet.org/api/v1/balance?api_key=' . rawurlencode($GLOBALS['settings']['microwallet_api_key']));
$request = '';
$request .= "GET /api/v1/balance?api_key=".rawurlencode($GLOBALS['settings']['microwallet_api_key'])." HTTP/1.0\r\n";
$request .= "Host: www.microwallet.org\r\n";
$request .= "Connection: close\r\n\r\n";
$fp = @fsockopen('ssl://104.28.0.112', 443);
if (!$fp) {
// ??
}
@fputs($fp, $request);
$response = '';
while (!@feof($fp)) {
$response .= @fgets($fp, 1024);
}
@fclose($fp);
$balance = explode("\r\n\r\n", $response);
$balance = $balance[1];
|
|
|
|
Thanks! 
|
|
|
|
Actually to avoid "connection timeout" the should be removed  3 seconds may not be enough for a heavily overloaded website. Thanks! |
|
|
|
Hi there, we are operating www.pinktussy.com and www.mezzacap.com and both sites are still not working because the API doesn't work. We've contacted the guys from microwallet.org but got no answer yet. I am pretty sure that they are very busy anyway with repairing the DDoS but they should inform about the situation. A lot of people depend on them - faucet sites are not working, referal systems are out of order (at least for the microwallet faucets). In one word - a large part of the ecosphere is down. I think it would be a good idea if @landofbicoin would drop a few words here and we all know a bit more, thx in advance. Cheers  Bluechipper Did you try to temporary replace: $fp = @fsockopen('ssl://www.microwallet.org', 443);
if (!$fp) {
return array(
'success' => false,
'message' => 'Failed to send.',
'html' => '<div class="alert alert-danger">Failed to send.</div>',
'response' => null,
);
}
@fputs($fp, $request);
with $fp = @fsockopen('ssl://www.microwallet.org', 443, $errno, $errstr, 3);
if (!$fp) {
return array(
'success' => false,
'message' => 'Failed to send.',
'html' => '<div class="alert alert-danger">Failed to send. ('.$errno.') '.$errstr.'</div>',
'response' => null,
);
}
@fputs($fp, $request);
in the code. Please paste the error message you get after "Failed to send." here. Hi, I have changed the code and got the error message: "Failed to send. (0)" You can try it with our test site http://bexxpal.com. Cheers Bluechipper Looks for some reason your hosting is unable to resolve the microwallet's IP address. As a temp measure you can ping locally: ping www.microwallet.orgthis will give you the IP 104.28.0.112, or 104.28.1.112 or something else ... Then replace $fp = @fsockopen('ssl://www.microwallet.org', 443, $errno, $errstr, 3);
$fp = @fsockopen('ssl://[put the IP here]', 443, $errno, $errstr, 3);
Then you will probably need to buy me a beer  just kidding, I'm not sure if it will work. Hello! I actually reset my account information to be able to say this - Haven't posted in a long time... But I really wanted to thank you for going out of your way to help other faucet owners. Unless it breaks a rule here (which I doubt it does) can you reply to this with your bitcoin address? It is written in my profile Don't forget the IP thing is temp measure. Wait 3 days and if the original code still does not work then check it with your hosting provider etc. If someone else get the IP in the future he may steal your API key etc. |
|
|
|
Hi there, we are operating www.pinktussy.com and www.mezzacap.com and both sites are still not working because the API doesn't work. We've contacted the guys from microwallet.org but got no answer yet. I am pretty sure that they are very busy anyway with repairing the DDoS but they should inform about the situation. A lot of people depend on them - faucet sites are not working, referal systems are out of order (at least for the microwallet faucets). In one word - a large part of the ecosphere is down. I think it would be a good idea if @landofbicoin would drop a few words here and we all know a bit more, thx in advance. Cheers Bluechipper Did you try to temporary replace: $fp = @fsockopen('ssl://www.microwallet.org', 443);
if (!$fp) {
return array(
'success' => false,
'message' => 'Failed to send.',
'html' => '<div class="alert alert-danger">Failed to send.</div>',
'response' => null,
);
}
@fputs($fp, $request);
with $fp = @fsockopen('ssl://www.microwallet.org', 443, $errno, $errstr, 3);
if (!$fp) {
return array(
'success' => false,
'message' => 'Failed to send.',
'html' => '<div class="alert alert-danger">Failed to send. ('.$errno.') '.$errstr.'</div>',
'response' => null,
);
}
@fputs($fp, $request);
in the code. Please paste the error message you get after "Failed to send." here. Hi, I have changed the code and got the error message: "Failed to send. (0)" You can try it with our test site http://bexxpal.com. Cheers Bluechipper Looks for some reason your hosting is unable to resolve the microwallet's IP address. As a temp measure you can ping locally: ping www.microwallet.orgthis will give you the IP 104.28.0.112, or 104.28.1.112 or something else ... Then replace $fp = @fsockopen('ssl://www.microwallet.org', 443);
$fp = @fsockopen('ssl://104.28.0.112', 443);
Then you will probably need to buy me a beer just kidding, I'm not sure if it will work. |
|
|
|
A majority of my referrals have accounts in microwallet faucets. It took months of constant advertising to gain these referrals. The way things are heading, it looks like I am going to lose all my referrals. Even if the faucet owners come up with a new micropayment cache system, will the members still be able to retain their referrals?
Yes: - If the websites continue running microfaucet - If you/they used bitcoin addresses (instead of username/email) - If the microwallet replacement uses bitcoin addresses - If the website admin decide to keep the microfaucet_users table Too many IFs  |
|
|
|
Hi there, we are operating www.pinktussy.com and www.mezzacap.com and both sites are still not working because the API doesn't work. We've contacted the guys from microwallet.org but got no answer yet. I am pretty sure that they are very busy anyway with repairing the DDoS but they should inform about the situation. A lot of people depend on them - faucet sites are not working, referal systems are out of order (at least for the microwallet faucets). In one word - a large part of the ecosphere is down. I think it would be a good idea if @landofbicoin would drop a few words here and we all know a bit more, thx in advance. Cheers Bluechipper Did you try to temporary replace: $fp = @fsockopen('ssl://www.microwallet.org', 443);
if (!$fp) {
return array(
'success' => false,
'message' => 'Failed to send.',
'html' => '<div class="alert alert-danger">Failed to send.</div>',
'response' => null,
);
}
@fputs($fp, $request);
with $fp = @fsockopen('ssl://www.microwallet.org', 443, $errno, $errstr, 3);
if (!$fp) {
return array(
'success' => false,
'message' => 'Failed to send.',
'html' => '<div class="alert alert-danger">Failed to send. ('.$errno.') '.$errstr.'</div>',
'response' => null,
);
}
@fputs($fp, $request);
in the code. Please paste the error message you get after "Failed to send." here. |
|
|
|
|
Show Posts
