@QuantumKiwi go troll somewhere else, welcome to my "ignore"
Topic: BitPay.com is online - page 3. (Read 9034 times)
Keep up the good work guys, this is really starting too look more like an attack on bitcoin, 4 days already
@QuantumKiwi go troll somewhere else, welcome to my "ignore"
@QuantumKiwi go troll somewhere else, welcome to my "ignore"
Really, im not impressed bitpay.
You have lost another customer.
No support? No replys? No direct support to merchants who GAIN you the profits, you take a percentage of our cut and we are getting little to no support.
Your telling us merchants with API's to modify the API ourselves...... Get real. Im getting a coder to code my own module and take my own payments.
Companies who do not respect clients and look after them in hard times - LOOSE CLIENTS.
Bye BitPay! Hello Quantum Kiwi BTC Pay!
You have lost another customer.
No support? No replys? No direct support to merchants who GAIN you the profits, you take a percentage of our cut and we are getting little to no support.
Your telling us merchants with API's to modify the API ourselves...... Get real. Im getting a coder to code my own module and take my own payments.
Companies who do not respect clients and look after them in hard times - LOOSE CLIENTS.
Bye BitPay! Hello Quantum Kiwi BTC Pay!
Bitpay is down right now. You should use global distributed servers to prevent DDoS.
we will get there. one problem at a time.
the CDN from cloudflare looks like a nice service to do just that.
Bitpay is down right now. You should use global distributed servers to prevent DDoS.
The DDOS protection we setup is breaking the client SSL certificate used in our API and all of the shopping cart plugins. However, it is blocking the attack and our site is reachable now.
We have recently added API keys as an easier authentication method for the API. The API keys are passing through the firewalls just fine.
if you are using our API, then please update your authentication method to replace the client SSL with the API key. instructions can be found here:
https://bitpay.com/downloads/bitpayApi.pdf
if you are using one of our cart plugins like Magento, WHMCS, opencart, or zen cart, we need to update all of these plugins to use the new auth method. If you are a programmer, you can update the plugin yourself using the instructions in the above link.
We are still under attack (for the 4th day in a row) so things are extremely busy right now. We will update the plugins as soon as we get time.
We have recently added API keys as an easier authentication method for the API. The API keys are passing through the firewalls just fine.
if you are using our API, then please update your authentication method to replace the client SSL with the API key. instructions can be found here:
https://bitpay.com/downloads/bitpayApi.pdf
if you are using one of our cart plugins like Magento, WHMCS, opencart, or zen cart, we need to update all of these plugins to use the new auth method. If you are a programmer, you can update the plugin yourself using the instructions in the above link.
We are still under attack (for the 4th day in a row) so things are extremely busy right now. We will update the plugins as soon as we get time.
I wouldn't mind it either, my previous idea had reference, but nobody wants to respond from the company not even by email. Give them the server IPs and let them ok those IPs.
We have resorted to making our own automated BTC payment system, we're almost done with it for WHMCS. Though we offer many other form's of payments most people don't like paying with CC from the BTC community. So instead of loosing clientele we have resorted to making our own, if it work's look's like bitpay has lost their first customer over this. Sorry guys but no communication is not good news.
We have resorted to making our own automated BTC payment system, we're almost done with it for WHMCS. Though we offer many other form's of payments most people don't like paying with CC from the BTC community. So instead of loosing clientele we have resorted to making our own, if it work's look's like bitpay has lost their first customer over this. Sorry guys but no communication is not good news.
So back to the point, how do we get our API's working properly again???
I wouldn't mind accepting peoples payments for services and get some bills paid
I wouldn't mind accepting peoples payments for services and get some bills paid
Well now my password is not working and the password reset page is not working. Anybody got any updates on this?
I just was able to get on the site and download the most recent whmcs module but no go, its still the old version. I emailed steve a while ago but no response yet, i know he's busy but if the merchants could at least use their sites. I sent in my servers ips under the hope that they would be allowed access maybe. A response or status report would be nice. I mean you have 1000 merchants just to be offline like this completely.
It's about WalletBit (which is already back online), not about BitPay, mate.
Sorry! I think I should go to sleep now
But tbh I wouldn't be surprised if this was not the same person / group of people.
Especially given recent DDoS ''offers'' in the marketplace.
It's about WalletBit (which is already back online), not about BitPay, mate.
Didn't the attacker state his motives? Is it for money, or what?
He asked for 1k BTC.
Any source?
Got this but saw it elsewhere too where I can't remember now
http://bitcoinmagazine.net/walletbit-under-ddos-1000btc-demanded/
Didn't the attacker state his motives? Is it for money, or what?
He asked for 1k BTC.
Any source?
I have a question, is Bitpay still doing ACH transfers out on a daily basis? Or are these also suspended during the attack? As I have a lot of cash in there right now that need's to be transferred out at the end of the day :S
ACH transfers are not interrupted. All funds are fully accounted for and banks are just fine.
Didn't the attacker state his motives? Is it for money, or what?
He asked for 1k BTC.
I have a question, is Bitpay still doing ACH transfers out on a daily basis? Or are these also suspended during the attack? As I have a lot of cash in there right now that need's to be transferred out at the end of the day :S
The redirect you can actually fix yourself in the php library file, under the curl class. I did this awhile ago as the updated WHMCS module wasn't on the site. But I have had this fix for awhile now and it is still giving me the invoice error. So it probably is the API as the original module is kind of old.
I too am getting an error when the customer is trying to checkout. I am guessing the API has to be updated. Steve could you please post/let us know when and how we should update our api. I might have a really old one as it is directing me to bit-pay.com/checkout
Thanks
Thanks
I'm getting the same thing, have been all day. I think it's with the API, I emailed steve and still waiting for a response back.
Im getting an invalid invoice error with my WHMCS api?
Regards,
Staff @ QuantumKiwi
Regards,
Staff @ QuantumKiwi
Jump to: