wallet: Copay can't connect to Wallet Service on Ubuntu/Kubuntu 14.04, 15.10, 16.04, Fedora 23 and ArchLinux

Copay 1.6.3 can’t connect to Wallet Service on Ubuntu/Kubuntu 16.04. Works fine on 15.10 before upgrade. Error message “Error at Wallet Service: Network connection error”.

[631:1229/201518:INFO:CONSOLE(13)] ""Profile loaded ... Starting UX."", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201518:WARNING:nss_ssl_util.cc(374)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[631:1229/201519:INFO:CONSOLE(13)] ""onGoingProcess" "openingWallet"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201519:INFO:CONSOLE(13)] ""onGoingProcess" "openingWallet" "null"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201519:INFO:CONSOLE(13)] ""Wallet Opened"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201520:INFO:CONSOLE(13)] ""Binding touchstart elements..."", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201520:INFO:CONSOLE(13)] ""onGoingProcess" "updatingStatus"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201520:INFO:CONSOLE(13)] ""Updating Status:" "Personal Wallet" "null"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201520:INFO:CONSOLE(13)] ""Updating Transaction History"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201520:WARNING:nss_ssl_util.cc(374)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[631:1229/201520:WARNING:nss_ssl_util.cc(374)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[631:1229/201520:INFO:CONSOLE(13)] ""Status update. hash:null Try:0"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201520:INFO:CONSOLE(13)] ""onGoingProcess" "updatingStatus" "null"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201520:WARNING:nss_ssl_util.cc(374)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[631:1229/201521:INFO:CONSOLE(13)] ""Client ERROR: " "{\"code\":\"CONNECTION_ERROR\"}"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201521:INFO:CONSOLE(13)] ""Showing err popup:Error at Wallet Service: Network connection error"", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (13)
[631:1229/201523:WARNING:nss_ssl_util.cc(374)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[631:1229/201523:INFO:CONSOLE(27)] ""[warn] Error receiving notifications."", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (27)
[631:1229/201524:WARNING:nss_ssl_util.cc(374)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[631:1229/201528:WARNING:nss_ssl_util.cc(374)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
[631:1229/201528:INFO:CONSOLE(27)] ""[warn] Error receiving notifications."", source: file:///tmp/.org.chromium.Chromium.JTC2c4/public/lib/angular.js (27)

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 77 (5 by maintainers)

Most upvoted comments

you can use the same servers Copay uses: bws.bitpay.com

On Fri, May 13, 2016 at 3:39 PM, tomtruitt notifications@github.com wrote:

@matiu https://github.com/matiu i do believe we need api… using the bitcore-wallet or bitcore-wallet-client it would need to connect to bitcore-wallet-service running on a bitcore-node correct? so we would need to run out own full node? or are their bitpay full-nodes we can utilize? looks like cost of running a full node on digital ocean will be $160 a month… not trying to spend that right now for a wallet api

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/bitpay/copay/issues/3723#issuecomment-219126093

Matías Alejo Garcia @ematiu Roads? Where we’re going, we don’t need roads!

matiu on May 13, 2016

Also, check bitcore-wallet-client and bitcore-wallet-server, is an API to access wallets is what you need.

matiu on May 13, 2016

We will apply this changes:

https://github.com/bitpay/bitcore-wallet-service/pull/437/files

to the stand alone BWS and install it in production in the next few days. I will update the ticket once it is live, so you can test again. Thanks a lot.

matiu on Feb 21, 2016

I have Ubuntu 16.04 running where this issue is reproducible. What I need to do to help you find if this related or not? How I can test different types of TLS connections? (If this can help.)

RussianNeuroMancer on Jan 17, 2016