Connecting to Network Issue


#1

I have reported the bug and sent pub file already but haven’t received any investigation result for 1 month so I would like to get some help from someone. I had more than 50,000 ADA in the wallet and its got stuck.

Issues:
On March 13th.

-I was using daedalous wallet without any issue but I decided to install daedalous wallet in a new Laptop.

-With a new laptop, I finished installing the wallet and put “10” recovery keys (I saved only 10 phrases and it was mistake. So I cannot recover the wallet by re-install). It was taking too much time processing, so I closed the wallet and restarted it.

-I don’t know what happened but when I restarted the wallet, it opened with balance “0”.

-I was afraid of losing ADA because of wallet bugs, so I tried to open daedalous wallet with my old laptop, but its stuck on “connecting to network” and never opens.

-I checked time sync and all the possible solutions but don’t work at all. I could use the wallet with my old laptop upto the point when I recovered the wallet in a new laptop.

Does anybody know how to fix this connecting to network issue? I have only 10 recovery keys so I cannot uninstall, install and recover. At first, I have to solve the issue and secure my ADA.


#2

This is bad, you need to keep Daedalus open, while it’s restoring or syncing.

Closing it has corrupted the local data most probably, so now it cannot show you proper wallet

Impossible to lose your coins because of wallet, until you yourself send a transaction to spend your ADA. Wallet just shows you what’s on the blockchain.

Wallets on separate computers are not connected in any way. It’s coincidence.

  1. For how long did you ways for the old wallet to connect?
  2. What version of the Daedalus you have on the old notebook?

Daedalus may “stick” at connection to network screen, but it does the right thing at the background, you just can’t see it. Usually solved just by waiting for a bot longer (up to few hours).

Try to just wait for few hours on the old notebook. On the new notebook you gonna have to delete the wallet inside Daedalus (the one that you have restored) and possibly remove the folder with all wallet data, and recover it again, but without closing the Daedalus. What operating system do you use?

I don’t know what this means.


#3

Thanks vantuz-subhuman a lot for your help.

Let me reply to your questions.

  1. For how long did you ways for the old wallet to connect?

I left it around 1 hour but it stuck on Connecting to Network. Should I leave it 1 day or so??

  1. What version of the Daedalus you have on the old notebook?

I am using 1.0.3769

  1. Regarding 10 keys, it should be 12 but I only recorded 10. So it means I cannot simply uninstall and install my old wallet, so I must move all my ADA to some other wallet.

#4

Yes. Unfortunately, 1 hour is not enough. It might take few hours. If it does not connect for a day - you might have to reinstall Daedalus.

Yes this is the solution in this case. But you shouldn’t try to restore your wallet from 10 words. You need to create completely new wallet, write down all 12 words this time, and then send all money from old wallet into new one.


#5

Try installing latest version of Daedalus from here https://daedaluswallet.io/#download. Before installing backup these two folders “Secret-1.0” and “Wallet-1.0” from %appdata%/Daedalus folder.

Even if installing new version doesn’t solve the issue try deleting the DB-1.0 folder from %appdata%/Daedalus folder.

Win:
Type %appdata% on the explorer’s address bar
Open Daedalus folder
Delete the content of DB-1.0

Mac:
On the Finder’s menu bar select Go
Click Go to Finder…
Type ~/Library/Application Support/Daedalus
Delete the content of the DB-1.0 folder

You cannot restore the wallet with only 10 words.


#6

Thanks a lot Jam.
The thing is, I do not have correct 12 keys, I only have 10 keys, this was my mistake.
So if I erase the wallet I cannot recover it forever, this is why I must to solve Connection issue to take ADA out from it.

If I take back up of those two folders from my old wallet, can I replace those and somehow open in the new wallet?


#7

Thanks vantuz, I will leave it open for a couple hours and see if it moves to the dashboard or not. I will let you know the status later, so please help me again till I safely move ADA to some other wallet


#8

Ventuz

I am glad to hear that theres no relations between old wallet and new corrupted wallet. Though it was really weird why I could recover 0 balance wallet with only 10 keys. People probably can cause same bugs just by entering 10 keys and kill the process while recovering.


#9

You can, copy “Secret-1.0” and “Wallet-1.0” folder from your old PC from this location …\AppData\Roaming\Daedalus and replace in %appdata%/Daedalus in your new PC (close the Daedalus before you replace the folder) and restart Daedalus.


#10

Jam

Really! even if they are newly installed wallet, its not gonna ask me recovery phrases if I replace those files?

One thing I worry about is that the versions of wallets are different.


#11

I didn’t test myself, you can try.


#12

Jam

Okay, I will test and see what happens.


#13

You probably have an old version of Daedalus, if it allows you to do this. In the latest version it is impossible, since it just shows you error message about wrong recovery phrase:


#14

Yes, right.
giving an error message should be the proper behavior. My wallet was 1.0.3769 or something so its not the latest.


#15

Jam

Now, I installed latest wallet to my new PC. copied Secret-1.0 and Wallet-1.0 from my old wallet in old PC. replaced those two folders. I opened Daedalus wallet in my new PC and it says Connecting to network.
I will try to leave it for some hours.


#17

Did you install the latest version over the existing wallet in your new PC? I recommend fresh installation of Daedalus.

Uninstall Daedalus, delete Daedalus folder under %appdata% folder and reinstall Daedalus.


#18

Jam

Yes, I deleted the wallet in my new PC and fully installed new wallet. I moved two folders, started and left it for 10 hours. But it did not move from Connecting to Network. it did not work.
So now, I erased new wallet again and re-installed again. This time, I will start it until the new wallet loads all Block trantaction to 100% and then replace two folders.


#19

Vantuz

I kept old wallet open for 10 hours but it did not solve the problem. It’s stuck on Connecting to Network.
As I looked at other pages, I found that some people could solve the issue by deleting DB-1.0 folder and using VPN.
I feel like that is the only one thing I can do currently.

Also, I looked at pub files and logs.
All the log files were updated until March 14th when I could access for the last time.
But some logs have exceptions from yesterday. Do you know why this happened?
It looks like connecting to port 8090 is failed?? Access is refused by Cardano server, is it??

If it does not harm old wallet, I may try deleting DB-1.0 folder and open the wallet via VPN again.
When to use VPN, which country should I choose? and do I need to change Time and location setting of my old PC in order to match that VPN location?

Now, these are the errors I found:

“stack”: “Error: connect ECONNREFUSED 127.0.0.1:8090\n at Object.exports._errnoException (util.js:1026:11)\n at exports._exceptionWithHostPort (util.js:1049:20)\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)”,

-This is the last part of log from cardano-node.log
[production:INFO:ThreadId 3] [2018-04-19 01:59:15.78 UTC] [Attention] Software is built with wallet part
[production:INFO:ThreadId 3] [2018-04-19 01:59:15.78 UTC] using configurations: ConfigurationOptions {cfoFilePath = “C:\Program Files\Daedalus\\configuration.yaml”, cfoKey = “mainnet_wallet_win64”, cfoSystemStart = Nothing, cfoSeed = Nothing}
[node:ERROR:ThreadId 3] [2018-04-19 01:59:16.00 UTC] ConfigurationParseFailure “C:\Program Files\Daedalus\\configuration.yaml” (AesonException “Error in ['mainnet_staging_short_epoch_wallet_win64'].core: When parsing the record coreConfiguration of type Pos.Core.Configuration.Core.CoreConfiguration the key memPoolLimitTx was not present.") cardano-node.exe: ConfigurationParseFailure "C:\\Program Files\\Daedalus\\\\configuration.yaml" (AesonException "Error in [‘mainnet_staging_short_epoch_wallet_win64’].core: When parsing the record coreConfiguration of type Pos.Core.Configuration.Core.CoreConfiguration the key memPoolLimitTx was not present.”)
: Conv 62, 73: Conv 5f, 43: Conv 5d, 92: Conv 31, 61: Conv 61, 93: Conv 2b, 94: Conv 25, 95: Conv 49}, outSpecs={49: Conv 5c, 67: Conv 60, 83: Conv 0, 4: Conv 5, 5: Conv 4, 37: Conv 5e, 6: Conv 7, 55: Conv 62, 73: Conv 5f, 43: Conv 5d, 13: Conv 0, 61: Conv 61}}

-This is the last part of log from Daedalus.log
[2018-04-19 07:58:19:0535] [debug] Connection Lost. Reconnecting …
[2018-04-19 07:58:19:0933] [debug] Connection Lost. Reconnecting …
[2018-04-19 07:58:19:0933] [debug] CardanoClientApi::syncProgress called
[2018-04-19 07:58:20:0531] [debug] CardanoClientApi::syncProgress called
[2018-04-19 07:58:20:0935] [error] CardanoClientApi::syncProgress error: {
“stack”: “Error: connect ECONNREFUSED 127.0.0.1:8090\n at Object.exports._errnoException (util.js:1026:11)\n at exports._exceptionWithHostPort (util.js:1049:20)\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)”,
“message”: “connect ECONNREFUSED 127.0.0.1:8090”,
“code”: “ECONNREFUSED”,
“errno”: “ECONNREFUSED”,
“syscall”: “connect”,
“address”: “127.0.0.1”,
“port”: 8090
}
[2018-04-19 07:58:21:0534] [error] CardanoClientApi::syncProgress error: {
“stack”: “Error: connect ECONNREFUSED 127.0.0.1:8090\n at Object.exports._errnoException (util.js:1026:11)\n at exports._exceptionWithHostPort (util.js:1049:20)\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)”,
“message”: “connect ECONNREFUSED 127.0.0.1:8090”,
“code”: “ECONNREFUSED”,
“errno”: “ECONNREFUSED”,
“syscall”: “connect”,
“address”: “127.0.0.1”,
“port”: 8090
}
[2018-04-19 07:58:21:0536] [debug] Connection Lost. Reconnecting …
[2018-04-19 07:58:21:0934] [debug] Connection Lost. Reconnecting …
[2018-04-19 07:58:21:0934] [debug] CardanoClientApi::syncProgress called
[2018-04-19 07:58:22:0531] [debug] CardanoClientApi::syncProgress called
[2018-04-19 07:58:22:0933] [error] CardanoClientApi::syncProgress error: {


#20

HI can anyone help me my wallet is not working. before its working and no drama at all but when I upgrade my Os to Mac OS high sierra and try to open my wallet this come up

i got the new version (1.1.1.152) what im going to do now? thanks


#21

It looks like you are facing similar issue. For me its too bad because I lost recovery keys as well…