Just add the following lines to your bitcoin.conf file:

rpcthreads=xxx

xxx is the number of your miners, like 100.

Save and close the file, then restart your bitcoin-qt. Everything should be fine by now.

I just encountered the same problem and solved it by try and error. The answer is: you need a longer password.

Your rpcpassword needs to be at least 20-digit long after Dogecoin 1.5.

The error message only said the rpcpassword should be secure, but failed to state the condition above.

讲的有几分道理，但对于两点我不太认同。

1.时机的判断
之前比特币被中国打后就是最低点，之后就不断回涨。接下来除非出现欧盟或美国政府禁止比特币这种大利空的消息(我个人认为不大可能出现)，不然每出现一个正面消息(ex.Zynga接受比特币、比特币ATM开始出货...)价格整体来说只会往上涨，现在不趁拉回时布局就迟了，等到央行大印钞时才进场那时已是高点。

2.比特币的政治能量
从比特币的本质来说，无论使用者是否有此自觉，任何一国人民无论该国政体为何，使用比特币就是脱离该国央行控制而进行经济活动。使用比特币交易、储存资产无法课税也无法追踪，如果这不是革命，那什么才是革命？当局不是笨蛋，迟早都会了解这一点。美国从交易平台下手，强迫平台用户必须认证才能交易，除了防治洗钱，日后也可按此课税。中国的反应就不会如此开明，先是明令禁止，当禁止不了时便会祭出更激烈的手段。

Hi ppl,

I didn't realize there was such a thread and bounty here until I read an article about "Mt. Gox Premium"
http://www.coindesk.com/mt-goxs-bitcoin-price-higher-than-rival-exchanges/

Okay to the point. I've successfully withdrawed $10K USD from Mt. Gox to my bank (in Taiwan).
Here are my evidences:

Mt.Gox account history screenshot
https://imageshack.com/i/jm3e9dj

My bank screenshot (sorry it's in Chinese)
https://imageshack.com/i/ne8cysj

I've been trying to withdraw money from Mt. Gox since last November, and till December did I get my money, with a huge 5% fees (10K * 5% = 500 USD!) for manual processing, plus 4x USD fees from my bank and intermediate bank. (That's why the numbers do not match.)

This withdrawal is extremely costly and slow, but I did it anyway, just to make sure they are still working.

I don't know if the 0.25 (or 1?) BTC bounty still exists and it's fine by me, but if it does, please send it to 1MVh1jL3szvthVbbWs8Ffczs4QCBNpyTDF

Hi, I'd like to request whitelist because I want to share my mining experience with other miners. After all, I know something currently not well known in this forum.
Example:
https://bitcointalk.org/index.php?topic=169305.0

I should post this message in the corresponding thread.

Hi everyone, I've been here for a long time without any posts, but now I find some problem that I have a solution. Since I don't have permission to post in other section, I could only post this here.

At this moment, when your mining rigs try to connect to Slush's pool with the newest guiminer (20121203), you may find that it will randomly show an error message:

"No connections could be made because the target machine actively refused it",

causing your rigs to idle.

Here is my workaround:

1.Fall back to guiminer 20120219.
2.Because this version of guiminer does not support Stratum, you also need Slush's mining proxy to operate normally without warning message.
3.Start proxy, and then change your guiminer pool site to Other (localhost), with the same id and password for your miners in Slush's pool. Although this would appear as Solo mining, actually you'll be mining in Slush's pool via proxy.

Hope this could help