After transferring some BTC to my counterwallet, I got the -32000 log in error that started this thread.
Tried both quick access URL and full password, but neither got me in. Tried incognito mode, same thing.
Tried counterwallet.coindaddy.io and am now back in and can see the BTC, but my other wallet addresses (which were empty, but still important) have disappeared. Any chance on getting those addresses back?
So I am a real, rank amateur. How would I switch between servers? And I tried, subsequently, to move some BTC or SWARM between wallets in my account, but got the same error. Still scratching my headâŚ
Between addresses in your wallet, I suppose.
While you can do that, you probably donât need to do that (unless you are deliberately âconsolidatingâ various assets on one of several addresses you have in your wallet, I guess?).
@something sorry, different wallets in my address. I am already on coindaddy, because counterwallet wouldnât let me back in after I transferrred some BTC this morning. So many bugs guys, this is getting really frustrating⌠I still canât send anything anywhere and seriously just want to take my BTC and go nowâŚ
Haha, @something I love the idea here and really want to be involved, I was just frustrated. For now, my BTC are where I feel they are more safe and movable. But Iâll stick around, cause I like you guys and half of the stuff is probably my (inexperienced) fault too
Just keep at it! I will learn code in the meanwhile and come back when I know what Iâm talking about.
andy⌠sorry your having issues. I just logged into counterwallet.coindaddy.io and was able to login and view my addresses without any issues. Please feel free to email me at jeremy@coindaddy.io if you have any issues with the coindaddy servers
@jdogresorg I really appreciate that, thanks I can see everything no problem, itâs just on sending that I get an error. Will give it a few days and see if I can send some SWARMCOIN again and will mail you if I run into the same problem.
I would say itâs not âveryâ buggy, it just has bugs
A lot of recent problems were caused by Bitcoin Core timeouts and they arenât Counterwallet or even Counterparty bugs.
Today Bitcoin Core on cw01.counterwallet.io was updated to a more recent version, although there are still at least two unresolved timeout bugs open at Bitcoin Github repo so it may not really help.
Counterparty server is dependent on Bitcoin Core so until these problems are fixed in Bitcoin Core weâll see periodic timeouts bubble up to Counterwallet.
Seriously nearly 100 posts going back a year about this and still happening?
Im getting this:
failoverAPI: Call failed (failed over across all servers). Method: get_normalized_balances; Last error: JSON-RPC Error: Type: Server errorCode: -32000Message: Got call_jsonrpc_api request error: timed out
The error message is just telling you that counterwallet is having problems communicating with the counterblock service. This is just a general error indicating failure.
this thread actually started in feb of this year, not last year
and J-Dog is right, the coindaddy servers are great because they get restarted more often. The counterwallet servers are now going to be restarted daily to help reduce this issue.
I can not log into my counterwallet. It gives this error:
failoverAPI: Call failed (failed over across all servers). Method: get_normalized_balances; Last error: JSON-RPC Error: Type: Server errorCode: -32000Message:
Bad status code returned: â503â. result body: â{âmessageâ: âServer
errorâ, âcodeâ: -32000, âdataâ: âCounterparty database is behind
backend.â}â.