Bitcoin Forum
May 12, 2024, 03:56:39 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin Core stuck at 'Connecting to peers' after lengthy sync  (Read 136 times)
zlin776 (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 23, 2022, 11:11:42 PM
 #1

I am running Bitcoin Core on Linux Mint, using a 1TB SSD. I typically get to around 50% sync, then I get stuck at 'Connecting to peers', and it appears that I am unable to connect to the network.

I have deleted my 'Blocks' and 'Chainstate' folders a couple of times, completely reinstalling Core, but the same problem occurs.

The debug log states the following:
2022-11-23T23:01:47Z connect() to 127.0.0.1:9050 failed after wait: Connection refused (111)

I have scoured the forum posts from various sources to no avail.

Any suggestions?
Be very wary of relying on JavaScript for security on crypto sites. The site can change the JavaScript at any time unless you take unusual precautions, and browsers are not generally known for their airtight security.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715486199
Hero Member
*
Offline Offline

Posts: 1715486199

View Profile Personal Message (Offline)

Ignore
1715486199
Reply with quote  #2

1715486199
Report to moderator
1715486199
Hero Member
*
Offline Offline

Posts: 1715486199

View Profile Personal Message (Offline)

Ignore
1715486199
Reply with quote  #2

1715486199
Report to moderator
1715486199
Hero Member
*
Offline Offline

Posts: 1715486199

View Profile Personal Message (Offline)

Ignore
1715486199
Reply with quote  #2

1715486199
Report to moderator
jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
November 23, 2022, 11:21:23 PM
 #2

Are you using it via tor or not?.

Have you tried deleting peers.dat when this happens or disabling antivirus (there might be a workaround for this if you run it in a virtual machine so you can keep your main machine secure but your virtual machine quarantined and sandboxed. Also deleting the blocks folder generally helps.more than deleting chainstate.
zlin776 (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 23, 2022, 11:26:20 PM
 #3

Are you using it via tor or not?.

Have you tried deleting peers.dat when this happens or disabling antivirus (there might be a workaround for this if you run it in a virtual machine so you can keep your main machine secure but your virtual machine quarantined and sandboxed. Also deleting the blocks folder generally helps.more than deleting chainstate.

Could you point me in the direction for instructions to use via Tor?

Tried deleting peers.dat to no avail.

I do not have any antivirus or firewalls enabled (Linux)
vv181
Legendary
*
Offline Offline

Activity: 1932
Merit: 1273


View Profile
November 24, 2022, 04:43:44 PM
Merited by ABCbits (1), Edwardard (1)
 #4

It seems the problem is on Tor's side. How do you install and configure Tor?

If the same log still concurred, try to trace both Bitcoin and Tor logs. Also, try to restart the tor process.

Code:
sudo tail -F /var/log/syslog | grep tor -i # monitor tor log
sudo systemctl restart tor # restart tor
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!