Quote from: ranzolu on July 20, 2012, 09:20:50 AM

Ok so,
I was using guiminer/phoenix to deepbit, now suddendly it does not connect anymore, even if the same config works with slushspool.
Here is the error I get:

Code:

2012-07-20 10:56:18: Listener for "deepbit" started
2012-07-20 10:56:19: Listener for "deepbit": [20/07/2012 10:56:19] Phoenix v1.6.2 starting...
2012-07-20 10:56:23: Listener for "deepbit": [20/07/2012 10:56:23] No JSON object could be decoded
2012-07-20 10:56:23: Listener for "deepbit": [20/07/2012 10:56:23] Failed to connect, retrying...
2012-07-20 10:56:38: Listener for "deepbit": [20/07/2012 10:56:38] No JSON object could be decoded
2012-07-20 10:56:38: Listener for "deepbit": [20/07/2012 10:56:38] Failed to connect, retrying...

Does anybody know ho to solve it?
Thanks!

Do you still use GPUs? If so, the best way to "solve" this problem is to switch over to LTC mining, abandon guiminer and most importantly, one of the least profitable pools, Deepbit. Profits are much higher for LtC mining and selling them for BTC than keep on mining BTC directly. If you want to mine LTC, you need to switch to reaper anyways. You can then sell your LTC for BTC at Btc-e.com for example.

If indeed you are mining Bitcoins with Singles, Minirigs or Asics I would still propose to switch to a better PPS pool. Deepbit is probably the last choice, only if all others get Ddosd simultaneously. Switch to another miner because Guiminer is no longer really maintained/supported. Guiminer doesn't come with an in-built back-up pool option, so if a pool does go down, guiminer will just sit there waiting. Most people therefore recommend cgminer.