search

bitpay / wallet

Bitpay Wallet (formerly Copay) is a secure Bitcoin and other crypto currencies wallet platform for both desktop and mobile devices.
http://bitpay.com/wallet
MIT License
3.78k stars 1.74k forks source link

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

Closed RussianNeuroMancer closed 7 years ago

RussianNeuroMancer commented 8 years ago

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)
tomtruitt commented 8 years ago

did you do all updates to system? sounds like updates broke it from what they were saying

cmgustavo commented 8 years ago

No, I didn't. I downloaded the ISO and didn't check the checkbox when asked to install updates.

cmgustavo commented 8 years ago

I 'll try upgrading the system.

tomtruitt commented 8 years ago

@matiu i do believe we need api.. using the bitcore-wallet or bitcore-wallet-client it would need to connect to bitcore-wallet-service connected to a bitcore-node correct? so we would need to run our 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

matiu commented 8 years ago

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!

JulianTosh commented 8 years ago

@tomtruitt You can also run your own node ( force your copay wallet to query your own Insight server for enhanced privacy). The node project is called Insight.

tomtruitt commented 8 years ago

@JulianTosh right but that is essenitally the same thing as running bitcore-node full bitcoin node which i started out saying will cost $160 month on digital ocean... unless i'm missunderstanding you

tomtruitt commented 8 years ago

unless you are suggesting that i can also run insight locally but i'd still be tied to someone else node

matiu commented 8 years ago

This could not yet be reproduced by any BitPay member. It could also be related to Cloudfare.

JulianTosh commented 8 years ago

This is a very disheartening response. I can reproduce it every time using the technique I specified on Mar 6.

Install Fedora 23 from DVD (no patches), run copay fine. Install patches (dnf update), copay breaks.

RussianNeuroMancer commented 8 years ago

Issue is still reproducible with latest Copay. And as I find I can't use Copay as Opera plugin, because Copay is not published in Opera plugins store, and plugin from Chrome store is incompatible with Opera.

JulianTosh commented 8 years ago

More debug info in the session log would go a long way to helping identify the problem/faulty sublayer. Not having a working native Linux app is a serious debbie downer.

JulianTosh commented 7 years ago

Installed 2.2.0 on a fully updated Fedora 23 workstation.

Still unable to create a wallet and getting this error:

[19531:0707/073008:WARNING:nss_ssl_util.cc(374)] Unknown SSL error -12218 (SSL_ERROR_ENCRYPTION_FAILURE) mapped to net::ERR_SSL_PROTOCOL_ERROR
JulianTosh commented 7 years ago

Session log reveals:

ongoingProcess creatingWallet null
Error creating wallet: Network connection error
Route change from: create to: preferencesGlobal
gabegattis commented 7 years ago

Today, I tested Copay 2.2.0 on Debian 8.3 and I could not reproduce the error. I can test on Fedora 23 later today.

JulianTosh commented 7 years ago

Can you detail your test steps? A fresh install from the DVD works fine if you don't update the system. Once you update, it stops working.

The steps I did on Mar 6 are reproducable.

https://github.com/bitpay/copay/issues/3723#issuecomment-192944999

gabegattis commented 7 years ago

@JulianTosh I had an existing debian install. I installed all the latest updates. Then I downloaded the 2.2.0 release, checked the sigs, unzipped it, and ran the app. I was able to create a new wallet with no problem. I was pointed at the default production BWS server.

I will check my kernel and openssl versions later and report back.

Have you tried using https://github.com/bitpay/bitcore-wallet-client by itself? That would help us determine if the bug is related to node-webkit.

JulianTosh commented 7 years ago

Going on a hunch from someone mentioning it may be related to this bug: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568

I upgraded the nss package and dependencies on a fresh DVD install of Fedora 23 and it immediately broke CoPay.

The exact packages I upgraded are:

# dnf update nss
Last metadata expiration check performed 0:27:21 ago on Thu Jul  7 11:06:31 2016.
Dependencies resolved.
=============================================================================================================
 Package                         Arch                Version                      Repository            Size
=============================================================================================================
Upgrading:
 nss                             x86_64              3.24.0-1.3.fc23              updates              863 k
 nss-softokn                     x86_64              3.24.0-1.0.fc23              updates              312 k
 nss-softokn-freebl              x86_64              3.24.0-1.0.fc23              updates              222 k
 nss-sysinit                     x86_64              3.24.0-1.3.fc23              updates               58 k
 nss-tools                       x86_64              3.24.0-1.3.fc23              updates              495 k

Not sure what to do with this information, but this is clearly the smoking gun on Fedora.

JulianTosh commented 7 years ago

Just for documentation purposes, on the DVD fresh install of Fedora, the versions of these packages are:

$ rpm -qa | grep ^nss
nss-3.20.1-1.0.fc23.x86_64
nss-softokn-3.20.1-1.0.fc23.x86_64
nss-softokn-freebl-3.20.1-1.0.fc23.x86_64
nss-sysinit-3.20.1-1.0.fc23.x86_64
nss-tools-3.20.1-1.0.fc23.x86_64
JulianTosh commented 7 years ago

Going on the discussion in the debian bug link, it appears they resolved it with a chromium-browser patch to fix compatibilty with nss 3.21. *https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/comments/47

I do not see any chromium packages installed on Fedora from what I can tell, so could it be a static link issue with the linux binaries?

matiu commented 7 years ago

Interesting. Probably when nodewebkit upgrades the bundled version of chromium, the issue will be fixed on Copay.

On Thu, Jul 7, 2016 at 4:08 PM, JulianTosh notifications@github.com wrote:

Going on the discussion in the debian bug link, it appears they resolved it with a chromium-browser patch to fix compatibilty with nss 3.21. * https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/comments/47

I do see any chromium packages installed on Fedora from what I can tell, so could it be a static link issue with the linux binaries?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bitpay/copay/issues/3723#issuecomment-231177137, or mute the thread https://github.com/notifications/unsubscribe/AAGCHEoxwruJ1tyO35Vy3nD61iA9TICUks5qTU68gaJpZM4G8Srb .

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

gabegattis commented 7 years ago

On my debian environment, I have libnss3 2:3.17.2-1.1+deb8u2. This is older than the 2:3.21-1ubuntu2 version from the bug report. That may explain why I was not having problems.

Debian has a newer version of libnss3 on unstable, but I have not tested that.

@RussianNeuroMancer @tomtruitt @john-light and others, can you guys check what version of nss you have on your system?

sputnik1458 commented 7 years ago

I am also getting this error when trying to create a new wallet. I am on Linux Mint 17.2 and have another box running 17.3 where it works perfectly fine.

john-light commented 7 years ago

@gabegattis what command should I run to check? libnss3 --version did not return any results.

gabegattis commented 7 years ago

@john-light if you are using apt as your package manager, you can run

apt version libnss3
JulianTosh commented 7 years ago

Just wanted to let everyone know that I just installed CoPay 2.6.0 binaries on a Fedora 24 Live workstation and it works fine. Only requirement is installation of the libXScrnSaver package.

matiu commented 7 years ago

@JulianTosh thanks a lot for the update. I was about to ask you guys to test again since we upgraded the underlying NW.JS framework on Copay 2.5.

thanks, and sorry the delay solving this issue.