3

Some suggestions... Relying on those publicly known/advertised nodes is probably a bad idea to start with. Lots of people use those as remote nodes for their wallets for example, so I'd expect the operators make sensible use of the limit-rate-... options. Which brings me to the next point, what limit settings are you using? You should set these according ...


3

This usually works, but I broke something when moving the seeder to a new set of servers. It should be working again soon!


3

Leaving aside exclusive peers, when a node starts for the very first time, it connects to the seed peer(s) to get an initial peer list. It then attempts to maintain at least 2 anchor peers (if it successfully handshakes with an attempted peer and doesn't already have enough anchor peers, it can be added to the anchor list). If an anchor node goes away, it ...


2

--rpc-bind-ip [IP ADDRESS] Binds the daemon to an IP address. You need to use your External IP if you plan to access this daemon from outside your local network, or an Internal IP if you only want it to work for devices in the same local network. --rpc-bind-ip 0.0.0.0 In the context of a local network, 0.0.0.0 means 'all the IP addresses inside the local ...


2

Pools use JSON over HTTP. To test connectivity, you can simply use curl on the mining port advertised in the "Getting started" page of most pools. This will cause an error message on the pool side since you don't "talk stratum", but is otherwise innocuous. Another possibility, which doesn't use "traditional Unix command line tools" but still uses command ...


2

With the new 0.13.0.4 Beryllium Bullet version of the daemon and CLI software, all is working fine under Linux. No more issues.


2

If uPNP won't cooperate, you can create a port forwarding rule (in Firewall > NAT > Port Forward) for the WAN interface that directs a destination of port 18080 to port 18080 of the internal IP of your node. This will have the effect of also creating a firewall rule on the WAN interface that allows the traffic arriving at port 18080 to pass through to the ...


2

This does not try all entries in the set, it picks one entry in that set.


1

When you setup your wallet, you will have had an option to use a Bootstrap Node. A bootstrap node allows you to use your wallet whilst your own full node is downloading the blockchain. This said (and assuming you didn't select to use a bootstrap node), the fact the GUI says it is not connected to the daemon suggests some other issue. Even though you can see ...


1

Anchor first, then white, then gray.


Only top voted, non community-wiki answers of a minimum length are eligible