search

iotaledger / legacy-wallet-use-trinity-wallet-instead

IOTA Wallet
GNU General Public License v3.0
2.07k stars 414 forks source link

"REQUEST ERROR" when trying to attach receiving address to tangle #434

Open NaN-Boiiiiii opened 6 years ago

NaN-Boiiiiii commented 6 years ago

Using the latest light wallet release. Please advise on how to fix this problem. Tried literally everything I was able to research..

NaN-Boiiiiii commented 6 years ago

Changed nodes and the curl option about 15 times and spammed the button, eventually it started working for me. now to manually generate a lot of addresses so that I get my balance back, lol

raul7angels commented 6 years ago

I have same problem, how did you fix it? And Is the dev team looking into this?

inatangle commented 6 years ago

Hi Guys,

Does 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 6 years ago

Same 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.

donaminos commented 6 years ago

I've got the same error and couldn't fix it even after deleting IOTA Folder et re-installing the app

inatangle commented 6 years ago

I 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 6 years ago

I have the light wallet 2.5.3 and I have the same problem

tommit1961 commented 6 years ago

with 2.5.4 "invalid response"

tommit1961 commented 6 years ago

i got it!

Berndinox commented 6 years ago

Maybe "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/

Berndinox commented 6 years ago

Problem still not solved after enabling attachToTongle. https://github.com/iotaledger/wallet/issues/465

NanukHe commented 6 years ago

the same problem with macintosh, but not on friend's HP elitebook

SerkanSipahi commented 6 years ago

I changed in "Edit Node Configuration" the Curl Impl. from Webgl2 to CCurl ! It work for me but i dont know the difference!

julianmlr commented 6 years ago

Same Problem here with light node on Windows x64. Tired many nodes servers...

BenRacicot commented 6 years ago

Same problem on 2.5.5 on Mac, this concerns me deeply.

dozme commented 6 years ago

same on mac, wallet 2.5.6 !!! FIX IT!

rish321 commented 6 years ago

+1, Any solution to this? bitfinex and ccurl also not working for me.

luiswill commented 6 years ago

Is reinstalling fixing the issue or is the network just congestioned ?

dozme commented 6 years ago

reinstalling didn't fix it

cyber2024 commented 6 years ago

Same on windows.

bencjedi commented 6 years ago

On 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 6 years ago

changing nodes a few times worked for me.

bencjedi commented 6 years ago

I 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 notifications@github.com 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 https://github.com/iotaledger/wallet/issues/434#issuecomment-354950196, or mute the thread https://github.com/notifications/unsubscribe-auth/APU5NLvjmHzCWHEMq4Wlxw_h-AFIWEizks5tGytagaJpZM4QXmAL .

AlexWick commented 6 years ago

@Bencjedi yes.

AlexWick commented 6 years ago

@Bencjedi not lost forever.... As long AS YOU HAVE YOUR PRIVATE KEY. 🔑

UmutAlihan commented 6 years ago

the tangle infrastructure is not stable yet that is sad :'/

same problem for me too

bencjedi commented 6 years ago

His 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 notifications@github.com wrote:

@bencjedi https://github.com/bencjedi yes.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iotaledger/wallet/issues/434#issuecomment-355056723, or mute the thread https://github.com/notifications/unsubscribe-auth/APU5NFiyFjU45H6Frz5M9eLn6bqMJMo7ks5tG6rZgaJpZM4QXmAL .