chainpoint / chainpoint-cli Goto Github PK

I keep getting this error whenever i try to submit a hash, i know this isnt the best information but im trying to upload to the bitcoinheader node. If anyone can give me any information would be great, Thanks

request to https://18.191.50.129/hashes failed, reason: write EPROTO 006888D8D07F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../ssl/record/rec_layer_s3.c:1586:SSL alert number 80

request to https://18.191.50.129/hashes failed, reason: write EPROTO 006888D8D07F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../ssl/record/rec_layer_s3.c:1586:SSL alert number 80

request to https://18.191.50.129/hashes failed, reason: write EPROTO 006888D8D07F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../ssl/record/rec_layer_s3.c:1586:SSL alert number 80

request to https://18.191.50.129/hashes failed, reason: write EPROTO 006888D8D07F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../ssl/record/rec_layer_s3.c:1586:SSL alert number 80

HASH | Unable to submit at this time, try again

This happens even when --server is specified.
README needs an update for the stuff envalid is doing.

Edit: Everything works fine on OSX. This error is happening on Ubuntu 16.04.

For example 👍
If i enter chp submit abfc4e95bcab8cf9dffdc61a7cb296644a3993505bc3d778d11ff7e7c932bb5e
i get the error Cannot read property 'length' of undefined
Can you check ?

Are there any examples of anchoring to ETH?

This is the error I get

Unable to discover a random Node instance

I've installed it throug npm

Even version outputs the error

> chp version
Unable to discover a random Node instance

Or even if I specify one of my nodes with -s http://123.123.123.123 (adding real ip) I get the same error

Love the idea, but is the project still alive, or just a victim of its own success and backend calendar servers overwhelmed with requests? I only ask as the issues area seems v quiet, and both of my attempts on a Mac M1 and x86 running Linux are the same:

$ chainpoint-cli-macos submit 8e985932695c7af7e3c4fc86389a35c0fe40109bbdb7886621540ec204c3dd92
8e985932695c7af7e3c4fc86389a35c0fe40109bbdb7886621540ec204c3dd92 | Unable to submit at this time, try again

$ chainpoint-cli-linux submit 8e985932695c7af7e3c4fc86389a35c0fe40109bbdb7886621540ec204c3dd92
8e985932695c7af7e3c4fc86389a35c0fe40109bbdb7886621540ec204c3dd92 | Unable to submit at this time, try again

The error is a little vague .. can it just not find an active server, or it's hitting a server that's not accepting requests for whatever reason, or something I'm missing in setting this up locally? I don't want to write a script to keep retrying to an already overwhelmed server, or something that just doesn't exist.