You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
This repository has been archived by the owner on Feb 26, 2021. It is now read-only.Using the latest light wallet release. Please advise on how to fix this problem. Tried literally everything I was able to research..
The text was updated successfully, but these errors were encountered:
raul7angels commented Nov 10, 2017I have same problem, how did you fix it? And Is the dev team looking into this?
inatangle commented Nov 13, 2017Does this error occur when trying to attach an address to an IRI ver 1.4.1.2 node with the 2.5.4 wallet? I also couldn't attach any addresses so uninstalled the wallet, went through and deleted all iota related directories manually, then reinstalled the wallet and I can now attach again.
Berndinox commented Nov 13, 2017Same here, with 2.5.4!
I've found it did work with bitfinex server and webgl mode. (Have to restart Wallet after switching)
While with most other servers it did not work.
I've got the same error and couldn't fix it even after deleting IOTA Folder et re-installing the app
inatangle commented Nov 15, 2017I can confirm that as my node is unlisted (i.e. not a public wallet node), the ddos theory does not work.
Completely deleting the 2.5.4 installation, including residual files left behind, will almost certainly resolve the problem. Check the user/appdata/local and user/appdata/roaming directories for 'Iotawallet' directories and delete those.
tommit1961 commented Nov 15, 2017I have the light wallet 2.5.3 and I have the same problem
tommit1961 commented Nov 15, 2017with 2.5.4 "invalid response"
tommit1961 commented Nov 15, 2017 Berndinox commented Nov 15, 2017Maybe "attachToTongle" on Server-Side is blocked, eg. Limited-API.
I've found that on the Docker-Image providing a headless full-node got this setting per default.
That will be fixed soon.
This message is only relevant if you do host your own node with docker:
https://hub.docker.com/r/bluedigits/iota-node/
Problem still not solved after enabling attachToTongle.
#465
the same problem with macintosh, but not on friend's HP elitebook
SerkanSipahi commented Dec 8, 2017I changed in "Edit Node Configuration" the Curl Impl. from Webgl2 to CCurl ! It work for me but i dont know the difference!
julianmlr commented Dec 21, 2017Same Problem here with light node on Windows x64. Tired many nodes servers.
BenRacicot commented Dec 22, 2017Same problem on 2.5.5 on Mac, this concerns me deeply.
dozme commented Dec 22, 2017same on mac, wallet 2.5.6 . FIX IT!
rish321 commented Dec 25, 2017+1, Any solution to this? bitfinex and ccurl also not working for me.
luiswill commented Dec 25, 2017Is reinstalling fixing the issue or is the network just congestioned ?
dozme commented Dec 25, 2017 •reinstalling didn't fix it
cyber2024 commented Dec 27, 2017Same on windows.
bencjedi commented Dec 28, 2017On Windows 7 and getting the same thing. I sent my IOTA from Binance to my receive address and then tried to attach the tangle, but get invalid response. Where is my IOTA? Once I can get attached to the tangle the IOTA should go into my wallet? or are they lost forever?
Cattleman commented Jan 3, 2018changing nodes a few times worked for me.
bencjedi commented Jan 3, 2018 via emailI did the same and finally it went. Tried to send some IOTA to my friend on Saturday and it is still pending. He needs to attach to tangle, so my balance can update in my wallet, right?
On Wed, Jan 3, 2018 at 2:25 AM, Cattleman ***@***.***> wrote: changing nodes a few times worked for me. — You are receiving this because you commented. Reply to this email directly, view it on GitHub , or mute the thread . AlexWick commented Jan 3, 2018 AlexWick commented Jan 3, 2018
@bencjedi not lost forever. As long AS YOU HAVE YOUR PRIVATE KEY. 🔑
UmutAlihan commented Jan 3, 2018 •the tangle infrastructure is not stable yet that is sad :'/
same problem for me too
bencjedi commented Jan 3, 2018 via emailHis wallet is just an address at Binance (just found out), so there's no mechanism for him to attach to the tangle for the verification processing to go through. How do we solve this one? I'd like to see the amount I sent him debited out of my wallet.
On Wed, Jan 3, 2018 at 11:29 AM, Alex ***@***.***> wrote: @bencjedi yes. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or mute the thread .