ematiu

Push notifications go thru Google/Apple servers, are not related to the '/bws/api/v1/notifications' api call. `/notifications` just pulls updates (if available) from the wallet. In the log I see queries every...

On Fri, Jan 29, 2016 at 10:59 AM, Dabura667 [email protected] wrote: > So > 1. No push notifications for private BWS. Only bws.bitpay.com? > > Unless you bundle you own...

what error are you getting? Make sure not to enter a space before of after the 12 words, the words are normally lowercase by sure to respect that. On Wed,...

AFAIK it has been never tested with self-signed certs. Also, IIRC the "cors" error is kind of "catch-all" error, so you may want to look that on the code (at...

Can you try the following? Using your server with http, check the request on the console log (accessing copay with google chrome) and grab the auth headers (x-identity and x-signature)...

signatures for GET requests cover the HTTP method and URL, so it should work. Be sure of including the ?r=xxx parameter. On Mon, May 18, 2015 at 12:07 PM, dabura667...

Thanks for the update! I think the 'untrusted ceritificate' error at curl is OK, that is what you get what you use self signed certs (there is no way for...

I am reviewing the code at bitcore-wallet-client, and I think I found an error regarding the `port` parameter. Could you try running the https server at the standard port and...

as a library, to access BWS. in bower.json, it depends on angular-bitcore-wallet-client, which depends on bitcore-wallet-client. On Wed, May 20, 2015 at 10:31 AM, dabura667 [email protected] wrote: > Copay is...

Hey, This is the setup we have at bitpay's servers, at config.js ``` https: true, privateKeyFile: '/etc/ssl/bws.bitpay.com.key', certificateFile: '/etc/ssl/bws.bitpay.com.crt', ``` ``` # cat /etc/ssl/bws.bitpay.com.key -----BEGIN RSA PRIVATE KEY----- [...] -----END...