Duniter can synchronize (i.e. download, verify and apply blocks) when running normally, but very slowly, and it can even be stuck. (this is suitable for catching up a few days or weeks, not more) That’s why you needed to resynchronize when your latest block was ~6000.
There are always a few errors, probably from badly configured nodes.
It means your node has not mined any block in the current window, so your custom difficulty cannot be computed. It will become a number as soon as you mine a block.
Private access means your node’s API is not publicly usable. You can enable public access with duniter wizard. (public WS2P is important; public BMA requires a good uptime and a static IP or domain name, and is useful for clients)
The difficulty is the difficulty of the proof of work : the higher, the harder it is to mine. (it needs more computation so statistically blocks are less frequent)
It increases to prevent someone to monopolize the blockchain, and hopefully to distribute equally the writing, independently from the computation power. (writing frequent blocks increase your difficulty to counterbalance your power)
Yes, it is, to distribute the load generated by the client, and to have an alternative when the default nodes are down. It will be even more when load-balancing clients will be used (tikka, gecko, cesium v2).
All the data exchanged in BMA already is or is meant to be public, so I think it’s not very important. At least right now.
What’s the command to enable public access? “duniter wizard” lack of one parameter… I’ve used “duniter wizard key” and “duniter wizard network” to set up my node, at firsts steps…
you can configure this from the webui, but just make sure the WS2P public access is set. You can find a sample configuration for your web server there (nginx):
So this way just set a private and public port (I’ve set 20901) and the websocket path, and you should get public access then.
You can also configure BMA but I haven’t manated to set it up for my part
Are you launching it with webstart?
Are you sure you connect to the right port?
Is this port open?
What is the output of curl 127.0.0.1:<duniter-webui-port> on the server itself?
You need to use duniter webstart instead of duniter start to have the web UI. (no need to run the two commands: webstart does all start does, plus the UI)
The web UI is a private web interface for monitoring the node (journal, status, peers, head, blocks mined…) and changing settings. It’s absolutely not necessary, everything can be done using only the config file and commandline.