Does anyone know why my Ethereum wallet on my desktop might have stopped being able to find peers? It was fine about 20 days ago. I loaded it yesterday, and I've been trying to get it to sync up using various techniques. I tried allowing it through my firewall, tried turning the firewall off, and tried to resync from scratch with the command line geth.exe --nat=none and that worked to download from scratch up to the 20 days ago, but when I loaded the GUI it still couldn't find peers. I had to close it and restart the computer, so I thought maybe I should try without turning the computer off in the process.
I'm not sure what the --nat=none command does. I just found it on a website. I am trying to put it on another computer with the same network, and had the same problems. Running the GUI it couldn't find peers. As soon as I used the geth.exe --nat=none command it started to load some of the blocks. It's downloading on and off right now. In the command prompt box it is saying that it failed a couple of times to find peers.
Some examples of errors:
"Failed with all peers <0 tries, 0 peers>"
"Failed with all peers <1 tries, 1 peers>"
"Synchronisation failed, dropping peer"
"retrieved hash chain is invalid"
"action from bad peer ignored".
I'm just confused, why the GUI can't find peers, but going through the command prompt would let it work, sometimes. I would think if the problem was that the firewall was blocking it then it would still be blocked even if I used the command line command and thus it wouldn't be able to find any peers ever.
I'm not sure what the --nat=none command does. I just found it on a website. I am trying to put it on another computer with the same network, and had the same problems. Running the GUI it couldn't find peers. As soon as I used the geth.exe --nat=none command it started to load some of the blocks. It's downloading on and off right now. In the command prompt box it is saying that it failed a couple of times to find peers.
Some examples of errors:
"Failed with all peers <0 tries, 0 peers>"
"Failed with all peers <1 tries, 1 peers>"
"Synchronisation failed, dropping peer"
"retrieved hash chain is invalid"
"action from bad peer ignored".
I'm just confused, why the GUI can't find peers, but going through the command prompt would let it work, sometimes. I would think if the problem was that the firewall was blocking it then it would still be blocked even if I used the command line command and thus it wouldn't be able to find any peers ever.