Stuck Connecting to Network

[cardinalproperty]

LOG.txt
I'm running Windows 10 and just installed the Daedalus wallet. It just hangs saying it's "Connecting to network..." I've reopened the app, and tried View > Reload, but it still just says it's connecting.

By connecting, does it mean it's downloading a blockchain or something? I'm accustomed to that taking a while with other wallets, but given that mainnet just launched I didn't think that would be it.

Let me know if I'm just being impatient (I gave it about 90 minutes the last time I launched it).

[darko-mijic]

cc @fersel

[fersel]

@cardinalproperty please take a look at our FAQ section at https://daedaluswallet.io/faq/ and see if that helps. If not, we'll need your node's logs (details on how to obtain them are provided on the same page).

[cardinalproperty]

@fersel thanks for the response. I read the FAQ section on what to do if you're stuck on that screen, but no dice.
I made sure nothing relevant was blocked by Windows Firewall, launched through the desktop shortcut and then through the .bat file, but still hung on connecting screen for several minutes.

I've attached the whole logs folder as a .zip.
Logs.zip

[cardinalproperty]

Bumping. I completely uninstalled and reinstalled the Daedalus wallet today, and this is still happening. Any insights on why?

[lowtempo711]

I have the same issue on Windows 8 ... It says on "connecting to network". Are there specific ports you have to open on your firewall for this wallet to work?

[hydro13]

I have helpt some users by : stop program. Rename or delete C:\Users\ "user-name" \AppData\Roaming\Daedalus
Reinstall from https://daedaluswallet.io/#download
Import your wallet
and its working 👍 the problem must be somwhere in AppData\Roaming\Daedalus

[cardinalproperty]

Thanks for the help, @hydro13; still no luck, but I appreciate the effort.

I tried reinstalling, and it's doing the connecting to network... thing now, but I'll let it run for a bit to see if a miracle happens, since the version number is higher than the last time I installed it. I bought some ADA as soon as it became available on bittrex, but it's still sitting on the exchange. I'll have to just sell it if I can't get the wallet to work.

[lowtempo711]

I tried to deleting the Daedalus folder from appdata directory and was able to reinstall the wallet. The wallet works until you shutdown the wallet and try to open the wallet again. When you try opening the wallet it just stays in the "Connecting to Network" stage......

[hydro13]

Your on a slow computer? edit your Daedalus.bat change --node-timeout 5 TO --node-timeout 30 save file.
you need to edit the file in notepad as administrator (run notepad as administrator)..
start the wallet with the bat-file
you can findt the bat file here on your comupter: C:\Program Files\Daedalus\daedalus.bat

the node-timeout will be updated in the next version of the wallet, but if you can't wait you can make the change your self :)

[domenkozar]

@cardinalproperty do you still have the issue?

[Jawabiscuit]

Hi, this is still an issue.

[lowtempo711]

No more issue. Thanks! From: J Avrin [mailto:notifications@github.com] Sent: Sunday, November 19, 2017 11:22 AM To: input-output-hk/daedalus Cc: lowtempo711; Comment Subject: Re: [input-output-hk/daedalus] Stuck Connecting to Network (#508) Hi, this is still an issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#508 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AfXYTYfzAEGv9YRF7kCZ_B336BUxw6PHks5s4H_LgaJpZM4PpZDV>.

[bitcartel]

Changing the timeout fixes the problem.

[csoroz]

Trying changing --node-timeout from 5 TO 30 as said above... still not working.

[csoroz]

The issue persist with the new version: Daedalus 1.0.3769

[humanoidcreature]

I have this also. Pretty frustrating.

[cleverca22]

@humanoidcreature are you on windows?, what the absolute path to your desktop? like C:\users\<username>\desktop ?

[humanoidcreature]

@cleverca22 I'm using Windows 10 and yes the path is correct. (I've got accent in my name, but it would be crazy if that's the problem.)

Edit: I replaced all %APPDATA% in the .bat file with the 'Short path' (<username>~1) and it's working now. So the accent was the problem in my name.

[cleverca22]

yep, there is a bug with unicode characters in your username

[csoroz]

I'm also using Windows 10 and my <username> is four ASCII chars, but the issue still persist.

[cleverca22]

@csoroz are there any obvious errors in C:\Users\USER\AppData\Roaming\Daedalus\Logs\cardano-node.log

[csoroz]

@cleverca22 Yes there are Timeout errors. I send you the Logs.zip

In daedalus.bat, variable %DAEDALUS_DIR% has an \ at the end, so some paths have a duplicated \. I have tried correcting that in the .bat file, but does not solve the problem.

[cleverca22]

@csoroz does your firewall/isp allow tcp port 3000 outgoing?

[csoroz]

@cleverca22 I have tried allowing port 3000 in windows firewall and also opening it in router configuration. No success...

Making ping to those ip addresses fails, for example:

C:>ping 13.115.112.96
Pinging 13.115.112.96 with 32 bytes of data:
Request timed out.

http://downforeveryoneorjustme.com/13.115.81.99

[cleverca22]

@csoroz normal ping is blocked, only tcp port 3000 is open, try something more like telnet and see if it can even connect

[csoroz]

Telnet to port 3000 seems to work but I only get a blank screen then finalizes...

[csoroz]

@cleverca22 Testing with http://portquiz.net:3000
I can reach port 3000.
Daedalus still fails to connect.

[lucianboboc]

I have the same problem on macOS Sierra with the last wallet version.
Also 9/10 times when i try to open the app it just jumps in the launch bar and then it remains there freezing "Application not responding".
I have this 2 problems since i first installed this app, what is going on?

[mimim-bkk]

So far the only way I found is to connect my macbook to 4G with my iPhone using personal hotspot and Daedalus can connect to the network and start to sync.
So my guess would be a router setup issue, I tried many combinations on port forwarding nor different network configurations but no success.
If someone have an idea how to setup the router to make it work, please share.

[gufmar]

As it looks like a noticeable number of users has problems using Daedalus just because their computer (AV Suite) or local network (LAN/WAN) does not allow connections to the 7 bootstrap servers listening on port 3000 I would suggest introducing a fallback on port 443 (HTTPS) or a complete switch to such a standard port.

[gufmar]

Also Windows 8/10 users should be averted that the current launch method (daedalus.bat in Start menu and on desktop) should be used to start the cardano-node and the daedalus wallet.

If after a first start the user right click the daedalus icon in the task bar to pin it there, this does only pin daedalus.exe. So on next start the wallet will stuck on "connecting to network..." because there is no cardone-node up & running.

[gufmar]

Last but not least both the possible issue with port 3000 and the task bar pinning should be mentionedn on the public FAQ page.

[csoroz]

For the first time I've seen Daedalus pass the screen "Connect to the network...". I haven't done anything special (maybe some Windows 10 update?). I left it for a while synchronizing with the network... when it was done, I closed the program. Subsequent runs failed again.
Now it has succeeded a second time...
Has successfully started several times, now...

[gufmar]

Note: I placed the request to use standard (well known) ports also on the devOps repository.
After I slept on it and reading about Daedalus philosophy (general crypto client, app store, ...) I believe the same thing should be considered for Daedalus current port 8090. When it becomes a light-weight client running on all kind of devices and in all kind of IP-networks, in order to connect to cardano-nodes using standard ports like 443 (usually used but not exclusively limited to https) wouldn't have any drawbacks. But it could avoid this small but definitively existing bunch of situations, where this connection attempts are blocked by some security/firewall rules.
So this is not rocket science or a special thing. But I would say it pairs very good with all your efforts to provide high assurance solutions.

[snajpa]

I have hit this this twice today on two different Windows 10 PCs. Daedalus log says ECONNREFUSED, I have yet to investigate why; but: those two machines are running localized Czech version of Windows, although they don’t use unicode chars in usernames. It syncs once, I can restore the wallet, but I can’t open Daedalus again after closing it (no, theres nothing running on :8090).

[csoroz]

It's working for me since my previous comment...

[2072]

I have the same problem on Windows 10 (using official build 1.0.3769). Tried all solutions mentioned in the FAQ to no avail.
There is no obvious error in the logs apart from a few "Reporting error" errors:

[node:INFO:ThreadId 3] [2018-01-21 19:21:55 UTC] Our verInfo: VerInfo { magic=2d964a09, blockVersion=0.1.0, inSpecs={96: Conv 43, 49: Conv 5c, 97: Conv 3d, 34: Conv 5e, 98: Conv 37, 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, 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}}
[node:DEBUG:ThreadId 3] [2018-01-21 19:21:55 UTC] startNode, we are NodeId 86521250-6f37-44dd-be9f-47c42600f006
[node:INFO:ThreadId 3] [2018-01-21 19:21:55 UTC] cardano-sl: commit 0c1fab91a7358fcb4c151a3a028ed650f7a36cbd
[node:INFO:ThreadId 3] [2018-01-21 19:21:55 UTC] Application: csl-daedalus:3, last known block version 0.1.0
[node:INFO:ThreadId 3] [2018-01-21 19:21:55 UTC] Genesis stakeholders (7 addresses, dust threshold 7 coin(s)): GenesisWStakeholders: {1deb8290: 1, 43011479: 1, 5071d880: 1, 5411c7bf: 1, 65904a89: 1, 6c9e1497: 1, af2800c1: 1}
[node:INFO:ThreadId 3] [2018-01-21 19:21:55 UTC] First genesis block hash: 89d9b5a5, genesis seed is 76617361206f7061736120736b6f766f726f64612047677572646120626f726f64612070726f766f6461
[node:INFO:ThreadId 3] [2018-01-21 19:21:55 UTC] Last known leaders for epoch epoch #0 are: [STRIPPED from the logs because it's really too long]
[node:INFO:ThreadId 3] [2018-01-21 19:21:55 UTC] Current tip header: GenesisBlockHeader:
    hash: 89d9b5a5b8ddc8d7e5a6795e9774d97faf1efea59b2caf7eaf9f8c5b32059df4
    previous block: 5f20df933584822601f9e3f8c024eb5eb252fe8cefb24d1317dc3d432e940ebb
    epoch: epoch #0
    difficulty: 0

[node.worker.subscription:NOTICE:ThreadId 561] [2018-01-21 19:21:55 UTC] dnsSubscriptionWorker: valency 1
[node.plugin:INFO:ThreadId 562] [2018-01-21 19:21:55 UTC] DAEDALUS has STARTED!
[node:ERROR:ThreadId 561] [2018-01-21 19:21:55 UTC] Reporting error with reason "Worker/plugin with logger name LoggerName {loggerName = "node"} failed with exception: ParseError {errorContexts = [], errorMessage = "not enough input", errorPosition = 1:1}"
[node.wallet.servant:INFO:ThreadId 579] [2018-01-21 19:21:55 UTC] 
GET
    :> api
    :> settings
    :> sync
    :> progress
   Status: OK 0s
[node.wallet.servant:INFO:ThreadId 588] [2018-01-21 19:21:55 UTC] 
GET
    :> api
    :> settings
    :> sync
    :> progress
   Status: OK 0s

the last log entry is then followed by countless similar node.wallet.servant:INFO entries with the exact same data apart from times and ThreadId

and occasionally by:

[node:ERROR:ThreadId 561] [2018-01-21 19:22:45 UTC] Didn't manage to report RError "Worker/plugin with logger name LoggerName {loggerName = \"node\"} failed with exception: ParseError {errorContexts = [], errorMessage = \"not enough input\", errorPosition = 1:1}" because of exception 'Failed to send a report, the exception was: HttpExceptionRequest Request {
  host                 = "report-server.cardano-mainnet.iohk.io"
  port                 = 8080
  secure               = False
  requestHeaders       = [("Content-Type","multipart/form-data; boundary=----WebKitFormBoundaryUmhUaEIpojUScQHk")]
  path                 = "/report"
  queryString          = ""
  method               = "POST"
  proxy                = Nothing
  rawBody              = False
  redirectCount        = 10
  responseTimeout      = ResponseTimeoutDefault
  requestVersion       = HTTP/1.1
}
 (ResponseBodyTooShort 218949 141)' raised while sending

Monitoring the process using process explorer shows that apart from listening locally on port 8090 and connecting to ec2-18-194-141-68.eu-central-1.compute.amazonaws.com on port 8080 at startup, cardano-node.exe is not attempting any connection to the outside.

Using process monitor, I can see it tries to open these non existant registry keys in loop:

HKLM\Software\Microsoft\Cryptography\Offload
HKLM\Software\Microsoft\Cryptography\DESHashSessionKeyBackward
HKLM\Software\Microsoft\Cryptography\Offload
HKLM\Software\Microsoft\Cryptography\DESHashSessionKeyBackward

At startup it also tries to access hundreds of non existant registry keys under HKLM/System

I hope this helps to track down the problem.

[2072]

Ok commit 3f7e033 put me on the track. it was a DNS issue for me: relays.cardano-mainnet.iohk.io does not always resolve using my configured DNS (several tries seem to be necessary which Cardano node is probably not doing). So like in the aforementioned commit I put addresses directly (the same as in the actual DNS record) and now it's syncing...

As seen in my previous post this problem does not appear to be logged which is another issue in itself.

[kk88london]

You guys are all super smart, I am not a techie, but I managed to fix my issue, after trying all the above. Not sure which change fixed it, but most likely switching from my home wifi to my mobile hotspot. It's now syncing. Let's see how that goes.

[mykitou]

Guys and girls, I just made my inscription because I think I found the problem. Create a new session in windows with admin rights, and in the name of the session do but input spaces or accents as é. Put a session name like user1 or admin for exemple.
Reinstall the wallet on the new session and executive the bat in the installation folder and everything right.
Sorry for my English I'm french.

Hop will help some of you

If you are happy make me happy

Ada

DdzFFzCqrhsyupVRGetsCTGkkZPrrotTmGaYrVipGjF4jf8DWQto5QSY6y7D3w7kUqzxBF57RDR5GK6yfbUtCVttATvtkdk8i8FH7e1m

[nikolaglumac]

Closing due to inactivity...