I’m trying to connect to my Duniter node via Sakia.
I have Duniter running on a Raspberry Pi 2 that’s running Yunohost.
admin@Xroklaus:~ $ sudo duniter status
Duniter is running using PID 1823.
I start Sakia on my home computer.
[folatt@Home sakia]$ sakia --currency=Guilder-Test
But run into this error:
Error connecting to the network : Error : No peer answered in community (0 peers available)
root_servers.yml
Guilder-Test:
display: European Basic Guilder Test
nodes:
4pDRn4BZqedUXQq2bvnrrJJeBhisZQjs9uq9BTMDQnaq:
- "BMAS folatt-duniter.nohost.me 443"
conf.json
{
"currency": "Guilder-Test",
"endpoints": [
"BMAS duniter-folatt.nohost.me 443"
],
"rmEndpoints": [],
"upInterval": 3600000,
"c": "0.000054218",
"dt": "86400",
"dtReeval": 2629800,
"ud0": "100",
"stepMax": 3,
"sigPeriod": "0",
"sigValidity": 31536000,
"msValidity": 31536000,
"sigQty": "3",
"xpercent": 0.9,
"percentRot": 0.6666666666666666,
"powDelay": "1200",
"avgGenTime": 960,
"dtDiffEval": 10,
"medianTimeBlocks": 20,
"httplogs": false,
"udid2": false,
"timeout": 3000,
"isolate": false,
"forksize": 100,
"switchOnHeadAdvance": 3,
"sync": {},
"port": 10901,
"msPeriod": 604800,
"loglevel": "info",
"cpu": 0.6,
"ipv4": "192.168.178.10",
"remotehost": "duniter-folatt.nohost.me",
"remoteport": "443",
"upnp": false,
"dos": {
"whitelist": [
"127.0.0.1"
],
"maxcount": 50,
"burst": 20,
"limit": 40,
"maxexpiry": 10,
"checkinterval": 1,
"trustProxy": true,
"includeUserAgent": true,
"errormessage": "Error",
"testmode": false,
"silent": false,
"silentStart": false,
"responseStatus": 429
},
"sigStock": "300000",
"sigWindow": 604800,
"idtyWindow": 604800,
"msWindow": 604800,
"rootoffset": 0,
"remoteipv6": "2001:983:8610:1:15e7:898b:aac8:6eff",
"ipv6": "2001:983:8610:1:15e7:898b:aac8:6eff",
"remoteipv4": "83.163.103.119"
}
[Update]
Changed BMAS to BMA_ENDPOINT_API. This returns the same error.
Also BASIC_MERKLED_API returns the same error.
[Update #2]
Changed back to BMAS and changed port 10901 to 443 on endpoint and sakia.
I still recieve the same error.
[Update #2]
Changed remote port 10901 to 443.
I still recieve the same error.