start local node with jormungandr --trusted-peer "/ip4/52.208.xx.xx/tcp/80" --genesis-block-hash 314c2e572306bc38450b3a4b87a4610bbe4b7ed962b03e05a06a096e6d6e07e7
Expected behavior
The node should start by executing the single jormungandr command. It seems we might need to add parameters for public_address and listen_address.
Additional context
OS: wind10
Network details: I am using a PC behind a router; Firewall enabled on local PC.
D:\iohk\otherProjects\jormungandr\scripts\connect-to-cluster\nicolas>jormungandr --trusted-peer "/ip4/52.208.xx.xx/tcp/80" --genesis-block-hash 314c2e572306bc38450b3a4b87a4610bbe4b7ed962b03e05a06a096e6d6e07e7
Sep 24 13:36:48.215 INFO Starting jormungandr 0.5.0 (HEAD-98922c77, release, windows [x86_64]) - [rustc 1.36.0 (a53f9df32 2019-07-03)], task: init
Sep 24 13:36:48.228 WARN Node started without path to the stored secret keys (not a stake pool or a BFT leader), task: init
Sep 24 13:36:48.230 INFO storing blockchain in memory, task: init Sep 24 13:36:48.232 INFO fetching block 314c2e572306bc38450b3a4b87a4610bbe4b7ed962b03e05a06a096e6d6e07e7 from 52.208.94.64:80, task: init
Error fetching the genesis block from the network
connection to peer failed
Describe the bug Error when starting the node with the provided single jormungandr command and the node is behind NAT/firewall.
Mandatory Information
To Reproduce Steps to reproduce the behavior:
jormungandr --trusted-peer "/ip4/52.208.xx.xx/tcp/80" --genesis-block-hash 314c2e572306bc38450b3a4b87a4610bbe4b7ed962b03e05a06a096e6d6e07e7
Expected behavior The node should start by executing the single
jormungandr
command. It seems we might need to add parameters forpublic_address
andlisten_address
.Additional context OS: wind10 Network details: I am using a PC behind a router; Firewall enabled on local PC.