legacy-wallet-use-trinity-wallet-instead
legacy-wallet-use-trinity-wallet-instead copied to clipboard
Connection Refused - IOTA light Wallet
I'm trying to login in to my wallet and it returns "Connection Refused"
IOTA Light Wallet 2.5.4 - IRI 1.4.1.2
I tried with all nodes and it returns the same problem. I tried creating new seeds, login with and succeseded. The only account that I can't have access is the one that have all my IOTA coins.
Hi, im facing the same issue with IOTA Light Wallet 2.5.4 - IRI 1.4.1.2 . Tried all available nodes multiple times during the last days, but no luck.
I mine on mineiota.com, the only transactions that I received are from that page. I have around 120 transactions on my wallet history.
@RamaDL yes, me too. around 96 transaction as i could look the last time and 4 adresses.
#512 Same issue here, I think the team will fix it soon.
Any solution? Not working... Still throwing Connection refused!
tengo el mismo problema alguna solucion
Same issue: connection refused after 124 transactions from mineiota.com
I have the same issue.
@th0br0?
Try this Change Node to custom and use this one. https://iota.thathost.net:443 It has been the only node i can find that is working.
I don't think it's that's the issue with hosts available. Connecting to that or other host, I got the same pattern:
- I can connect (and use) two other wallets.
- This wallet gave different errors: 'access denied', 'failed to connect to host' and takes a lot of time to login until it comes back to the login screen again.
I can connect (and use) two other wallets. This wallet gave different errors: 'access denied', 'failed to connect to host' and takes a lot of time to login until it comes back to the login screen again.
I have the exact same problems too. I have +110 transactions from mineiota.
Here's the limitation of the nodes on the tangle https://www.reddit.com/r/Iota/comments/7exwyq/psa_dont_use_mineiotacom_or_other_similar/
@onemoreitguy thx for the link.
But in the cases above everybody seems far away from the limit of 1000. Just round about 100 - 200 transactions so far.
android or desktop wallet version report the same. @ColDrekken , I didn't look at the code, but the 1000 limit could include cascading between nodes and/or simultaneous wallet requests
I have the exact same issue. I had 3 transactions in my wallet. Waiting patiently for the new wallet but it is frustrating not being able to access my wallet. Any news on when the new version of the wallet will be released?
what shall we do?
Still getting this error. When it will be resolved?
No luck so far on updates. Trying to build a full sync node with the compiled workaround. But takes quite some time :(
Is there any information when the new wallet will be released to resolve this problem? I've had the issue for 2-3 weeks and can't access any coins to do anything.
I might have a temporary workaround, but I cannot solve it because I cannot find/connect to fully sync neighbor nodes (my current subtangle is not solid... missing a few transactions) :(
What can we do to help?
need a reliable full sync tcp node to connect to. As long as my subtangle is not solid, the wallet fails to complete the load :( ... stuck on Latest Solid Milestone Index: 296598
Change node? Does not work, even using node.dance site! Install and unistall wallet, Does not work!! Install Iota Android, change pc or is a issue in your network. Does not work! If you have many transactions...i have only 5 txs.
This is many of several advices, none works!!!! IT IS NOT A USER ISSUE!!!!
My seed doesnt work in wallet IOTA Light Wallet 2.5.4, and the unique place where i get something was in smidgen/bitfinex lib. I see my pretty balance.
Miota price is skyrocketing.. Arrghhh, so much mixed feelings! We're doomed? Please devs help us..... :(
I cannot log in either. Using IOTA Light Wallet 2.5.4 and my host is iota.bitfinex.com:80
It will say LOGGING IN... and then after 15-20 minutes it says Connection Refused
We failed to connect because we made a lot of transactions in MINEIOTA.COM though.. We exceeded the limit of 1000 outgoing and incoming transactions. IMO I still have high hopes in IOTA foundation devs. Let us just wait for the next compliance.
Help us 😔
Someone suggested using https://github.com/MichaelSchwab/iota-commandline-wallet
Any thoughts on the project?
@vicman10000 Just letting you know I've gone through the steps but unfortunately even command line does not work. It looks like it still relies on running a full node as you have to edit java files to increase memory limit. Found here: https://iotatangle.slack.com/files/U1VE8FAPN/F2A9HCV28/current_workaround_for_connection_refuse.txt - Unfortunately I'm not great enough to understand Java enough to customize and I can't find any guides to get into that part of it.
The issue is the node/client don't currently handle wallets with large transactions
The 'connection refused' is a standard error response to the client based on the real server response to the transaction limit exceed (you can see it using a wireshark http trace)
I already managed to build a 'read-access-synced' (transactions not allowed) node, saw my wallets and tested successfully with other stressed users
If you kept your seeds private everything is safe. Just wait for a newer version of the wallet.
just to clarify everyone:
-
I'm not part of the dev team. Just a project enthusiast and follower as an IT guy
-
the dev team has no access to your wallets or seeds (I hope not !).
For impending transactions taking forever, Try configuring your node as attached.
Then, identify the earliest transaction you created (if you did more than one or tried, if you didn't let me know your situation)
Reattach the earliest pending transaction with positive balance first, thenrebraodcast. go to receive. generate an address and let your computer do some work. Then, chill and wait while. Let me know if this works or if doesn't. You can follow me on twitter for postings in regard to IOTA, the wallet, and a troubleshoot guide I am trying to compile this weekend.
On Wed, Dec 6, 2017 at 11:32 AM, Panda [email protected] wrote:
The issue is the node/client don't currently handle wallets with large transactions
The 'connection refused' is a standard error response to the client based on the real server response to the transaction limit exceed (you can see it using a wireshark http trace)
I already managed to build a 'read-access-synced' (transactions not allowed) node, saw my wallets and tested successfully with other stressed users
If you kept your seeds private everything is safe. Just wait for a newer version of the wallet.
just to clarify everyone:
I'm not part of the dev team. Just a project enthusiast and follower as an IT guy
the dev team has no access to your wallets or seeds (I hope not !).
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/iotaledger/wallet/issues/558#issuecomment-349732340, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac-6w_lx9-nbihrHJG_jumWYTiE0X6JBks5s9t2pgaJpZM4QvX5R .
For impending transactions taking forever, Try configuring your node as attached.
Then, identify the earliest transaction you created (if you did more than one or tried, if you didn't let me know your situation)
On Wed, Dec 6, 2017 at 11:32 AM, Panda [email protected] wrote:
The issue is the node/client don't currently handle wallets with large transactions
The 'connection refused' is a standard error response to the client based on the real server response to the transaction limit exceed (you can see it using a wireshark http trace)
I already managed to build a 'read-access-synced' (transactions not allowed) node, saw my wallets and tested successfully with other stressed users
If you kept your seeds private everything is safe. Just wait for a newer version of the wallet.
just to clarify everyone:
I'm not part of the dev team. Just a project enthusiast and follower as an IT guy
the dev team has no access to your wallets or seeds (I hope not !).
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/iotaledger/wallet/issues/558#issuecomment-349732340, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac-6w_lx9-nbihrHJG_jumWYTiE0X6JBks5s9t2pgaJpZM4QvX5R .