-
Notifications
You must be signed in to change notification settings - Fork 48
Problems with changing node #168
Comments
|
What 3 values do you enter? You are neither synced with default nor with values from https://thetangle.org/nodes btw: the not responding iota.cool server is another issue. I think that is hard coded for the tangle explorer. |
I enter "Node protocol" (ex. http://eugene.iota.community:14265) and "Node port" (ex. 14265). I never enter "Node IP" because I do not find it in the information about nodes. But if I understand you right, my wallet won´t work even if I manage to change the node? I would still have to wait for the iota.cool server to be repaired? Does it make more sense for me to enter for ex. Light wallet with my existing seed and try to change my node there? Thank you for your efforts to help me out with this. I really appreciate it. |
Ahh okay here we go
Protocol is ONLY http so enter http in node protocol
node IP is missleading here. It schould say "node ip or dns. So enter eugne.iota.community in node ip
Last set the port to 14265
Gesendet mit Blue
Am 21. Feb. 2018, 12:48, um 12:48, Penelopo <[email protected]> schrieb:
…I enter "Node protocol" (ex. http://eugene.iota.community:14265) and
"Node port" (ex. 14265). I never enter "Node IP" because I do not find
it in the information about nodes.
But if I understand you right, my wallet won´t work even if I manage to
change the node? I would still have to wait for the iota.cool server to
be repaired? Does it make more sense for me to enter for ex. Light
wallet with my existing seed and try to change my node there?
Thank you for your efforts to help me out with this. I really
appreciate it.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#168 (comment)
|
I also get the "Network error, could not connect to iota.cool server" error. It's because iota.cool is down. Changing the node does not help, because the domain is hardcodet in the sourcecode. Also it is not important for the basic functionality of the wallet. Like sayed above, the iota.cool server was only for providing information about the tangle (not needed) To the new error younow get: https |
Thank you so much for all your time. Now it looks like the thing is working, even if in a slow motion. I am trying to make a transaction, but it goes really slowly. Can I ask you for your Iota adress, so that I can send you a few of them in return for all the help? |
Yea, the Wallet is slow and buggy. But the IOTA-Team is working on a new Wallet called trinity. So it's not worth to put more effort in this one. If you are more interested in Iota join the community on Discord (https://discordapp.com/invite/fNGZXvh) |
I have already tried to reach you by email with this issue. As I have not got any response, I am posting my problem here:
Whenever I try to send my Iotas I get the message: "Network error, could not connect to iota.cool server".
I tried to change node but my attempts were unsuccessful (I also ticked PoW in settings), it only writes: "Node protocol not allowed".
Concerning this, I have a couple of questions:
Can we expect iota.cool server node to start working again soon? Is there any work done concerning this problem?
Why is it impossible for me to change the node? Are also other people having the same problems? (Because I doubt I did anything wrong in the procedure of trying to change the node.)
Can I log into Iota light wallet with the same seed I am using with android wallet?
Thanks in advance.
The text was updated successfully, but these errors were encountered: