Quote from: fragilefungi on April 20, 2018, 02:24:01 PM

The number of connections that you have makes me think that it could be a problem with the wallet. I used to always be able to get over 10 connections. My windows wallet has been open a day now and it only has 4 connections, and one of those is me. The linux wallet only had 2 connections until I did getpeerinfo on the windows wallet and added them to the .conf file on the linux wallet with connect=

Could you please post a node list of the ips that print out when you do getpeerinfo?

Unfortunately my node list wouldn't help much when they all are incoming connections from (non-public, non-listening) nodes as you won't be able to open a connection to them.
Since my last post connections have constantly decreased and are now at 6 connections.

I decided to setup another seed node and add it to dns to further avoid the possibility of splits/forks. No need to add any addnodes to your config, your client should find them and from there your node should get more addressess to try to connect to.

Quote from: fragilefungi on April 21, 2018, 04:54:24 AM

...
connect=coins.prohashing.com:6267
connect=157.161.128.53
connect=24.128.132.71
...

I would strongly suggest not to use connect=, the command line help says:

Code:

-connect= Connect only to the specified node(s)

Emphasis is on only which is probably not what you want.

If then addnode= should be your choice probably:

Code:

-addnode= Add a node to connect to and attempt to keep the connection open

But sine now one of the three seed address in the wallet points to four working IP addresses you should actually need nothing at all to get connected.

HTH