# Counterwallet login issues?

**URL:** <https://forums.counterparty.io/t/counterwallet-login-issues/926>\
**Category:** Counterwallet\
**Created:** [February 21, 2015, 10:38pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926 "2015-02-21T22:38:57Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![Andy\_Tudhope](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/andy_tudhope/32/324_2.png) [@Andy\_Tudhope](https://forums.counterparty.io/u/Andy_Tudhope)\
**Post date:** [June 22, 2015, 1:52pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/81 "2015-06-22T13:52:50Z")

</div>

Hi,

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](http://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?

Andy

---

<div class="post-metadata">

**Author:** ![Andy\_Tudhope](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/andy_tudhope/32/324_2.png) [@Andy\_Tudhope](https://forums.counterparty.io/u/Andy_Tudhope)\
**Post date:** [June 22, 2015, 2:05pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/82 "2015-06-22T14:05:07Z")

</div>

And another issue. I want to send some swarmcoin to a friend, but get this message:

Sorry, we got an error when trying to do the requested action: 'JSON-RPC Error:  
Type: Server error

Code: -32000

Message: Got call\_jsonrpc\_api request error: timed out

’ (API method: create\_send).

Looking at the Javascript, this seems to be the issue:

Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience.

Any suggestions for someone who knows very little about code?

---

<div class="post-metadata">

**Author:** ![something](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/something/32/240_2.png) [@something](https://forums.counterparty.io/u/something)\
**Post date:** [June 22, 2015, 4:58pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/83 "2015-06-22T16:58:49Z")

</div>

That about deprecated request might be just a warning, but not an error.

Probably it was just a transient error.  
You can try some other wallet server (or retry on the same server), e.g. CoinDaddy’s CW server.

---

<div class="post-metadata">

**Author:** ![Andy\_Tudhope](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/andy_tudhope/32/324_2.png) [@Andy\_Tudhope](https://forums.counterparty.io/u/Andy_Tudhope)\
**Post date:** [June 22, 2015, 5:13pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/84 "2015-06-22T17:13:19Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![something](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/something/32/240_2.png) [@something](https://forums.counterparty.io/u/something)\
**Post date:** [June 22, 2015, 6:11pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/85 "2015-06-22T18:11:21Z")

</div>

@Andy_Tudhope, never mind, just retry, and if it doesn’t work, try [https://counterwallet.coindaddy.io/](https://counterwallet.coindaddy.io/)

> [@Andy\_Tudhope](#):
>
> And I tried, subsequently, to move some BTC or SWARM between wallets in my account, but got the same error

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?).

---

<div class="post-metadata">

**Author:** ![Andy\_Tudhope](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/andy_tudhope/32/324_2.png) [@Andy\_Tudhope](https://forums.counterparty.io/u/Andy_Tudhope)\
**Post date:** [June 22, 2015, 8:14pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/86 "2015-06-22T20:14:28Z")

</div>

@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… ☹

---

<div class="post-metadata">

**Author:** ![Andy\_Tudhope](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/andy_tudhope/32/324_2.png) [@Andy\_Tudhope](https://forums.counterparty.io/u/Andy_Tudhope)\
**Post date:** [June 22, 2015, 9:09pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/87 "2015-06-22T21:09:50Z")

</div>

here’s some of the sorry story of tying to send 100 measly swarmcoin:

1Fq5NELqSyGyc6wPDENuBcN7wGNBA79KyV  
counterwallet-deps-min.js:405 [22/6/2015 22:6:28.129] [socket.io](http://socket.io) message received: disconnect - data:undefined  
counterwallet-deps-min.js:405 [22/6/2015 22:6:28.130] [socket.io](http://socket.io)(messages): The client has disconnected from server: [https://counterwallet.coindaddy.io](https://counterwallet.coindaddy.io)  
counterwallet-deps-min.js:405 [22/6/2015 22:6:28.635] [socket.io](http://socket.io) message received: reconnecting - data:1000  
counterwallet-deps-min.js:405 [22/6/2015 22:6:28.732] [socket.io](http://socket.io) message received: connecting - data:“websocket”  
counterwallet-deps-min.js:405 [22/6/2015 22:6:29.27] [socket.io](http://socket.io) message received: reconnect - data:“websocket”  
counterwallet-deps-min.js:405 [22/6/2015 22:6:29.28] [socket.io](http://socket.io) message received: connect - data:undefined  
counterwallet-deps-min.js:405 [22/6/2015 22:6:29.28] [socket.io](http://socket.io)(messages): Connected to server: [https://counterwallet.coindaddy.io](https://counterwallet.coindaddy.io)  
[https://counterwallet.coindaddy.io/\_api](https://counterwallet.coindaddy.io/_api) Failed to load resource: the server responded with a status of 504 (Gateway Time-out)  
counterwallet-min.js:13 1Fq5NELqSyGyc6wPDENuBcN7wGNBA79KyV

---

<div class="post-metadata">

**Author:** ![Andy\_Tudhope](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/andy_tudhope/32/324_2.png) [@Andy\_Tudhope](https://forums.counterparty.io/u/Andy_Tudhope)\
**Post date:** [June 23, 2015, 12:01am UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/88 "2015-06-23T00:01:17Z")

</div>

I can’t even see my history: “failoverAPI: Call failed (failed over across all servers). Method: get\_raw\_transactions; Last error: undefined”

---

<div class="post-metadata">

**Author:** ![something](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/something/32/240_2.png) [@something](https://forums.counterparty.io/u/something)\
**Post date:** [June 23, 2015, 7:17am UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/89 "2015-06-23T07:17:06Z")

</div>

I can understand the frustration… Can’t blame you for trying another wallet.

History can be (also) seen at [blockscan.com](http://blockscan.com) (e.g. [https://blockscan.com/address?q=1Fq5NELqSyGyc6wPDENuBcN7wGNBA79KyV](https://blockscan.com/address?q=1Fq5NELqSyGyc6wPDENuBcN7wGNBA79KyV)).

---

<div class="post-metadata">

**Author:** ![Andy\_Tudhope](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/andy_tudhope/32/324_2.png) [@Andy\_Tudhope](https://forums.counterparty.io/u/Andy_Tudhope)\
**Post date:** [June 23, 2015, 2:05pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/90 "2015-06-23T14:05:38Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jdogresorg](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/jdogresorg/32/1349_2.png) [@jdogresorg](https://forums.counterparty.io/u/jdogresorg)\
**Post date:** [June 23, 2015, 7:42pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/91 "2015-06-23T19:42:27Z")

</div>

andy… sorry your having issues. I just logged into [counterwallet.coindaddy.io](http://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](mailto:jeremy@coindaddy.io) if you have any issues with the coindaddy servers 🙂

---

<div class="post-metadata">

**Author:** ![Andy\_Tudhope](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/andy_tudhope/32/324_2.png) [@Andy\_Tudhope](https://forums.counterparty.io/u/Andy_Tudhope)\
**Post date:** [June 23, 2015, 8:12pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/92 "2015-06-23T20:12:39Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![FoldingCoin](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/foldingcoin/32/218_2.png) [@FoldingCoin](https://forums.counterparty.io/u/FoldingCoin)\
**Post date:** [June 24, 2015, 12:38pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/93 "2015-06-24T12:38:34Z")

</div>

Counterwallet is still very buggy, I would suggest using the chrome extension that i have had zero problems with  
[https://chrome.google.com/webstore/detail/ltb-companion-wallet/jmjmgcgkbndiepapjbcabhdbbhmmkhmj?utm\_source=chrome-ntp-icon](https://chrome.google.com/webstore/detail/ltb-companion-wallet/jmjmgcgkbndiepapjbcabhdbbhmmkhmj?utm_source=chrome-ntp-icon)

Its a great tool for just using counterparty assets, though you cannot create assets through it, using the assets works perfectly

---

<div class="post-metadata">

**Author:** ![something](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/something/32/240_2.png) [@something](https://forums.counterparty.io/u/something)\
**Post date:** [June 30, 2015, 7:05pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/95 "2015-06-30T19:05:20Z")

</div>

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](http://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.

---

<div class="post-metadata">

**Author:** ![BittBurger](https://avatars.discourse-cdn.com/v4/letter/b/50afbb/32.png) [@BittBurger](https://forums.counterparty.io/u/BittBurger)\
**Post date:** [August 4, 2015, 10:27pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/96 "2015-08-04T22:27:00Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jdogresorg](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/jdogresorg/32/1349_2.png) [@jdogresorg](https://forums.counterparty.io/u/jdogresorg)\
**Post date:** [August 5, 2015, 1:10am UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/97 "2015-08-05T01:10:35Z")

</div>

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.

Try using [counterwallet.coindaddy.io](http://counterwallet.coindaddy.io) …should work fine for ya 😄

---

<div class="post-metadata">

**Author:** ![FoldingCoin](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/foldingcoin/32/218_2.png) [@FoldingCoin](https://forums.counterparty.io/u/FoldingCoin)\
**Post date:** [August 5, 2015, 6:47pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/98 "2015-08-05T18:47:42Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![faceface](https://avatars.discourse-cdn.com/v4/letter/f/43a26b/32.png) [@faceface](https://forums.counterparty.io/u/faceface)\
**Post date:** [August 5, 2015, 11:03pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/99 "2015-08-05T23:03:49Z")

</div>

Thank you!

---

<div class="post-metadata">

**Author:** ![MrCheek](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@MrCheek](https://forums.counterparty.io/u/MrCheek)\
**Post date:** [August 26, 2015, 11:56am UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/100 "2015-08-26T11:56:01Z")

</div>

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.”}’.

---

<div class="post-metadata">

**Author:** ![something](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/something/32/240_2.png) [@something](https://forums.counterparty.io/u/something)\
**Post date:** [August 26, 2015, 12:02pm UTC](https://forums.counterparty.io/t/counterwallet-login-issues/926/102 "2015-08-26T12:02:46Z")

</div>

Known issue that’s been explained many times - retry in 90 mins or go to Coindaddy’s instance ([counterwallet.coindaddy.io](http://counterwallet.coindaddy.io)).

See here about time it takes to recover from these reorgs.

> [@\[WARNING\] Blockchain reorganisation](https://forums.counterparty.io/t/warning-blockchain-reorganisation/1417):
>
> Reparsing all transactions occurs once or twice a day. Why does it happen? How can I avoid it? counterpartyd doesn’t accept any requests during the reparsing. It takes over 1 hours in my server spec (Ubuntu 4G memory). It is a very serious problem for production running. 2015-08-08-T02:27:51+0900 [WARNING] Blockchain reorganisation at block 368821. 2015-08-08-T02:27:51+0900 [INFO] Reparsing all transactions. 2015-08-08-T05:22:07+0900 [INFO] Database minor version number updated. 2015-08-08-T06:…

I’ll now close this topic because it’s not the same issue for which topic was created (a forgotten passphrase, most likely).

[Previous page](https://forums.counterparty.io/t/counterwallet-login-issues/926.md?page=4)

[Next page](https://forums.counterparty.io/t/counterwallet-login-issues/926.md?page=6)
