Cannot connect to Duniter node: status code != 200 => 502

Support
1

Still not connecting…

[me@MyComputer sakia]$ sakia --currency=Guilder-Test --debug
[7118] PyInstaller Bootloader 3.x
[7118] LOADER: executable is /opt/sakia/sakia.bin
[7118] LOADER: homepath is /opt/sakia
[7118] LOADER: _MEIPASS2 is NULL
[7118] LOADER: archivename is /opt/sakia/sakia.bin
[7118] LOADER: Extracting binaries
[7118] LOADER: Executing self as child
[7118] LOADER: set _MEIPASS2 to /opt/sakia
[7118] LOADER: LD_LIBRARY_PATH=/opt/sakia
[7119] PyInstaller Bootloader 3.x
[7119] LOADER: executable is /opt/sakia/sakia.bin
[7119] LOADER: homepath is /opt/sakia
[7119] LOADER: _MEIPASS2 is /opt/sakia
[7119] LOADER: archivename is /opt/sakia/sakia.bin
[7119] LOADER: Already in the child - running user's code.
[7119] LOADER: Python library: /opt/sakia/libpython3.5m.so.1.0
[7119] LOADER: Loaded functions from Python library.
[7119] LOADER: Manipulating environment (sys.path, sys.prefix)
[7119] LOADER: Pre-init sys.path is /opt/sakia/base_library.zip:/opt/sakia
[7119] LOADER: sys.prefix is /opt/sakia
[7119] LOADER: Setting runtime options
[7119] LOADER: Initializing python
[7119] LOADER: Overriding Python's sys.path
[7119] LOADER: Post-init sys.path is /opt/sakia/base_library.zip:/opt/sakia
[7119] LOADER: Setting sys.argv
[7119] LOADER: setting sys._MEIPASS
[7119] LOADER: importing modules from CArchive
[7119] LOADER: extracted struct
[7119] LOADER: callfunction returned...
[7119] LOADER: extracted pyimod01_os_path
[7119] LOADER: callfunction returned...
[7119] LOADER: extracted pyimod02_archive
[7119] LOADER: callfunction returned...
[7119] LOADER: extracted pyimod03_importers
[7119] LOADER: callfunction returned...
[7119] LOADER: Installing PYZ archive with Python modules.
[7119] LOADER: PYZ archive: out00-PYZ.pyz
[7119] LOADER: Running pyiboot01_bootstrap.py
[7119] LOADER: Running pyi_rth_qt5.py
[7119] LOADER: Running pyi_rth_multiprocessing.py
[7119] LOADER: Running pyi_rth_pkgres.py
[7119] LOADER: Running main.py
DEBUG:meta:prepare:Initializing meta database
DEBUG:meta:upgrade_database:Begin upgrade of database...
DEBUG:meta:upgrade_database:End upgrade of database...
DEBUG:network:add_connector:AbE4R connected
DEBUG:node:connect_current_block:[AbE4R] Websocket block WSServerHandshakeError : 502, message='Invalid response status'
DEBUG:node:connect_peers:[AbE4R] Websocket peer WSServerHandshakeError : 502, message='Invalid response status'
DEBUG:node:safe_request:[AbE4R] status code != 200 => 502 (<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
)
DEBUG:node:request_current_block:[AbE4R] Could not connect to any BMA endpoint
DEBUG:node:safe_request:[AbE4R] status code != 200 => 502 (<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
)
DEBUG:node:request_peers:[AbE4R] Could not connect to any BMA endpoint
DEBUG:node:connect_current_block:[AbE4R] Websocket block WSServerHandshakeError : 502, message='Invalid response status'
DEBUG:node:safe_request:[AbE4R] status code != 200 => 502 (<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
)
DEBUG:node:request_current_block:[AbE4R] Could not connect to any BMA endpoint
DEBUG:node:connect_peers:[AbE4R] Websocket peer WSServerHandshakeError : 502, message='Invalid response status'
DEBUG:node:safe_request:[AbE4R] status code != 200 => 502 (<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
)
DEBUG:node:request_peers:[AbE4R] Could not connect to any BMA endpoint
DEBUG:node:safe_request:[AbE4R] status code != 200 => 502 (<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
)
DEBUG:node:request_peers:[AbE4R] Could not connect to any BMA endpoint
DEBUG:blockchain:initialize_blockchain:Requesting blockchain parameters
DEBUG:network:stop_coroutines:Start closing
DEBUG:network:stop_coroutines:Closing 1 websockets
DEBUG:network:stop_coroutines:Closed
ERROR:quamash._QEventLoop:Task was destroyed but it is pending!
task: <Task pending coro=<NetworkService.discovery_loop() running at sakia/services/network.py:178> wait_for=<Future pending cb=[Task._wakeup()]>>
[7118] LOADER: Back to parent (RC: 0)
[7118] LOADER: Doing cleanup
[7118] LOADER: Freeing archive status for /opt/sakia/sakia.bin

Daemon

folatt@Gildurklaus:~ $ systemctl --user status duniter.service
● duniter.service - Duniter node
   Loaded: loaded (/usr/lib/systemd/user/duniter.service; enabled)
   Active: active (running) since Tue 2018-01-16 07:09:29 UTC; 6min ago
  Process: 1835 ExecStart=/usr/bin/duniter webstart (code=exited, status=0/SUCCESS)
 Main PID: 1887 (duniter_default)
   CGroup: /user.slice/user-9514.slice/user@9514.service/duniter.service
           └─1887 duniter_default

Configuration


folatt@Gildurklaus:~ $ cat ~/.config/duniter/duniter_default/conf.json 
{
 "currency": "Guilder-Test",
 "endpoints": [
  "BASIC_MERKLED_API guilder-test.eu.org 80"
 ],
 "rmEndpoints": [],
 "upInterval": 3600000,
 "c": "0.000054218",
 "dt": "86400",
 "dtReeval": 2629800,
 "ud0": "100",
 "stepMax": 3,
 "sigPeriod": "0",
 "sigValidity": 31536000,
 "msValidity": 31536000,
 "sigQty": "3",
 "xpercent": 1,
 "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": 80,
 "msPeriod": 604800,
 "loglevel": "info",
 "cpu": 0.6,
 "ipv4": "192.168.178.30",
 "remotehost": "guilder-test.eu.org",
 "remoteport": "80",
 "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:2239:6fcb:6144:21d2",
 "ipv6": "2001:983:8610:1:2239:6fcb:6144:21d2",
 "remoteipv4": "None"
}

Firewall settings

admin@Gildurklaus:~ $ sudo yunohost firewall list -r
ipv4: 
  TCP: 
    - 22
    - 25
    - 53
    - 80
    - 443
    - 465
    - 993
    - 5222
    - 5269
    - 10901
  UDP: 53
ipv6: 
  TCP: 
    - 22
    - 25
    - 53
    - 80
    - 443
    - 465
    - 993
    - 5222
    - 5269
    - 10901
  UDP: 53
uPnP: 
  TCP: 
    - 22
    - 25
    - 53
    - 80
    - 443
    - 465
    - 993
    - 5222
    - 5269
    - 10901
  UDP: 53
  enabled: False

Modem settings

image
image.png1605×361 51.1 KB

2

I think duniter people may know this issue. @Moul ?

3

I’m already told this:

(11:12:17 AM) vit: folatt: creating a new currency is a special process where you need to 
generate manually the block zero. It is not fully documented on purpose. You should start by 
participate to the g1-test currency to test your node installation without risk. Then ask for 
certifications to be a member in g1-test.