legacy-wallet-use-trinity-wallet-instead
legacy-wallet-use-trinity-wallet-instead copied to clipboard
Connection Refused when using personal fully synced node
Prerequisites
If you are not suggesting a feature, you must be able to check all of the following (place an x inside the brackets to check the box). If you cannot check all of the boxes, this issue should not be reported on GitHub as it is not a bug:
- [x] I confirm that this is an issue with the IOTA Wallet and not an exchange
- [x] I confirm that this is an issue with the wallet, not IRI
- [x] For pending transactions: I confirm that I have tried reattaching and promoting multiple times (check this box if your issue is not related to a pending transaction)
- [x] I confirm that this is not an issue related to stolen/lost funds
- [x] For private key warnings: I confirm that I am not at risk of reusing an address, or another user has verified that I am not (check this box if your issue is not related to a private key reuse)
- [x] I confirm that this issue is present on the latest version of the wallet
Description
I am unable to connect the latest version of the Light Wallet (2.5.6) to my own full node. I know for sure that I am able to connect to my node via IP, and via localhost (via port forwarding). This is confirmed via curl, as well as going to tools -> node info in the Light wallet.
❯ curl http://localhost:14265 \
-X POST \
-H 'Content-Type: application/json' \
-H 'X-IOTA-API-Version: 1' \
-d '{"command": "getNodeInfo"}'
{"appName":"IRI","appVersion":"1.4.1.6","jreAvailableProcessors":4,"jreFreeMemory":974584288,"jreVersion":"1.8.0_151","jreMaxMemory":9544663040,"jreTotalMemory":4205838336,"latestMilestone":"EALVWEJTTNWNNFCUQOQXIMINIKEPPYXANVXPDBPUKFZNTEG9MMN9KDWIJPCOFFMKIQLLHQHQ9GJNA9999","latestMilestoneIndex":322899,"latestSolidSubtangleMilestone":"VFDIATMRNTGZYNQTNJNOBAPVEIZUPNZWAAQPXFCYQJEYCWAMZPGOGPDNGT9FXFVBBGLPJUCTQLTGZ9999","latestSolidSubtangleMilestoneIndex":322858,"neighbors":19,"packetsQueueSize":0,"time":1515450656033,"tips":1217,"transactionsToRequest":0,"duration":1}%
When I try to login with a previously used seed I get a "Connection Refused" error. Furthermore, when using a new seed, it tries to connect for a couple minutes but then times out with no error.
I know my full node is using latest version as of this post (1.4.1.6) and is running the latest milestone. I am not sure why the wallet cannot connect when using my server. I am able to login using the same seeds when using a public node.
Steps to Reproduce
-
Open wallet
-
Go to
Tools -> Edit Node Configuration -
Host =
Customand usehttp://localhost:14265orhttp://<my full node ip>:14265 -
Save
-
Go to
Tools -> View Node Infoand verify node info is correct (it's the same as thecurloutput from above)
-
Close Node info
-
Enter previously used seed. Will get "Connection Refused"
-
Enter new seed. Will try to connect for a couple minutes and then time out with no error.
Expected behavior:
Should be able to login using my fully synced node.
Actual behavior:
Connection Refused / Timeout
Versions
[OS Version] - macOS High Sierra
[Wallet Version] 2.5.6
I can confirm I'm also getting this issue, I'm unable to connect my wallet to my node.
I'm also getting this issue, I'm unable to connect my wallet to my node too.