search

SemkoDev / field.cli

WE HAVE MOVED TO A NEW REPOSITORY
https://gitlab.com/semkodev/field.cli
ISC License
34 stars 7 forks source link

Invalid response from node #25

Closed joshirio closed 6 years ago

joshirio commented 6 years ago

I'm trying to use smidgen multisig tool from bitfinex and when using carriota field as the node provider, it is not able to handle the response. When using other nodes like https://nodes.thetangle.org:443 everything is fine.

$ smidgen get-balance "XFAELMMFKBKNGAYLKNFOLHMOTAM9IVOLABDLNKNWUIFK9QJXEJKGAUHMEPMYPGLPFBWZAXJMFZYCWMQEAFMGNQKVFZ" --provider "https://field.carriota.com:443"
ERR! Received invalid response from node. 
ERR! Retry command or try to use another node. 
ERR! 
ERR! Use --provider to switch node.
$ smidgen get-balance "XFAELMMFKBKNGAYLKNFOLHMOTAM9IVOLABDLNKNWUIFK9QJXEJKGAUHMEPMYPGLPFBWZAXJMFZYCWMQEAFMGNQKVFZ" --provider "https://nodes.thetangle.org:443"
Balance: 218884849054300 (218884849.0543 Mi)

Is it possible that your response it not standard compliant? Or maybe it is a bug on smidgen's side, although I read others having similar issues with different tools...

joshirio commented 6 years ago

Another example is the isf-jclient from iotaspam.com

[2018-02-28 09:33:16] [NodeMngr] [DBG] node 'https://field.carriota.com:443' [0] is not synced (sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target), changing node to 'http://127.0.0.1:14265'

m1ndgames commented 6 years ago

Afaik the golang module also does it, but its not a bug, but a feature ;) The Cert chain is missing, see: https://www.ssllabs.com/ssltest/analyze.html?d=field.carriota.com&s=216.58.194.211

Or verify yourself: openssl s_client -showcerts -connect field.carriota.com:443

romansemko commented 6 years ago

This should be fixed now. Added the correct SLL certificates chain to the load balancer.

joshirio commented 6 years ago

Thank you, works now!