Author

Topic: Peer discovery problem (Read 166 times)

newbie
Activity: 3
Merit: 0
February 05, 2018, 03:36:04 PM
#6
So I think I found out the issue, i tried with 10 running VPS instances and it seemed to manage a connection. It seems maybe 3-4 may not have been enough. Going to retest it again tonight just to make sure it's all good.

sr. member
Activity: 490
Merit: 389
Do not trust the government
February 05, 2018, 09:23:12 AM
#5
Are you using Tor by any chance?
Maybe your ISP is blocking your clearnet (or Tor for that matter) connections to the Bitcoin network.
legendary
Activity: 2814
Merit: 2472
https://JetCash.com
February 05, 2018, 04:01:25 AM
#4
Maybe it is related to my problem then. I'm starting to wonder if there is some sort of node selection system in operation. I disconnect manually if a peer has a ping in the nn,nnn ms range if I see it, but that is probably a function of network congestion rather than wallet options. Are there any wallet options that I should enable to make my wallet more acceptable to other nodes?
newbie
Activity: 3
Merit: 0
February 04, 2018, 04:26:56 PM
#3

 it isn't unfortunately, and there are no errors in debug.log which is strange. Anyone encountered similar problems or able to possibly assist me with a diagnosis?
legendary
Activity: 2814
Merit: 2472
https://JetCash.com
newbie
Activity: 3
Merit: 0
February 04, 2018, 01:44:23 PM
#1
For some reason new peers aren't being discovered after connecting to hardcoded nodes. New users always have constant amount of connections (only the nodes, that are hardcoded in the wallet). What could be the cause of seed nodes not 'sharing' the connected peers with other peers?
Jump to: