Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getNextAddress ssl error #13

Open
xianggy opened this issue May 3, 2021 · 2 comments
Open

getNextAddress ssl error #13

xianggy opened this issue May 3, 2021 · 2 comments

Comments

@xianggy
Copy link

xianggy commented May 3, 2021

The JS code:
const wallet = new Wallet({
protocol: 'https',
hostname: '47.241.90.20',
port: 9256,
caCertPath: './xch_ssh/private_ca.crt',
certPath: './xch_ssh/private_daemon.crt',
keyPath: './xch_ssh/private_daemon.key',
});
wallet.getNextAddress('1').then(console.log);

got errors:
(node:55573) UnhandledPromiseRejectionWarning: Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: IP: 47.241.90.20 is not in the cert's list:
at Object.checkServerIdentity (tls.js:297:12)
at TLSSocket.onConnectSecure (_tls_wrap.js:1507:27)
at TLSSocket.emit (events.js:315:20)
at TLSSocket._finishInit (_tls_wrap.js:932:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:706:12)
at TLSWrap.callbackTrampoline (internal/async_hooks.js:131:14)

So which ssl files should the params caCertPath, certPath, keyPath point to ?

@JordyBaylac
Copy link
Contributor

Can you try omitting all arguments? Just use new Wallet()

@xianggy
Copy link
Author

xianggy commented May 3, 2021

It difficult, because the wallet node is running on another Ubuntu device.
So any other solutions please or Can I set the server not to verify the client?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants