Quote from: educatedwarrior on June 26, 2013, 12:15:38 PM

Quote from: salfter on June 26, 2013, 04:24:55 AM

Quote from: BTCsckr on June 26, 2013, 03:54:35 AM

After Cryptsy DDoS i´m getting this error

  File "./PyCryptsy/PyCryptsy.py", line 106, in GetAvailableBalance
   r=self.Query("getinfo", {})
  File "./PyCryptsy/PyCryptsy.py", line 71, in Query
   raise Exception("unable to decode response")
Exception: unable to decode response

anybody else with the same problem?

When I first logged into Cryptsy after the DDoS, I was redirected to a page with a captcha. I'm guessing the same thing is happening with API access.

Yes, same problem here

...and it's still there. Trying to pull up Cryptsy with either Lynx or Links just comes back with an error from Incapsula. "Protecting" an API URL with a captcha that can't be answered by services that use the API is a Bad Idea. The mining rig running CryptoSwitcher is headless; getting a graphical browser running so I can answer the stupid captcha will entail installing NX, a window manager, and Firefox; that's going to take some time, and even after all that there's still no guarantee that CryptoSwitcher will work again. Angry

I've put a request in with Cryptsy support:

Quote

Can Incapsula be set to not block API calls? With the example code at https://www.cryptsy.com/pages/api, an exception is thrown:

Code:

PHP Fatal error: Uncaught exception 'Exception' with message 'Invalid data received, please make sure connection is working and requested API exists' in /home/salfter/cryptsy-test.php:42
Stack trace:
#0 /home/salfter/cryptsy-test.php(46): api_query('getinfo')
#1 {main}
thrown in /home/salfter/cryptsy-test.php on line 42

Fatal error: Uncaught exception 'Exception' with message 'Invalid data received, please make sure connection is working and requested API exists' in /home/salfter/cryptsy-test.php:42
Stack trace:
#0 /home/salfter/cryptsy-test.php(46): api_query('getinfo')
#1 {main}
thrown in /home/salfter/cryptsy-test.php on line 42

This is what's being returned by Cryptsy on the API call:

Code:

It's also broken CryptoSwitcher as a consequence, if Cryptsy is enabled.

For the time being, if you disable auto-trading with Cryptsy, CryptoSwitcher will continue to work.