07/30/2022, 8:40 PM
how to find why these 2 nodes 1,2 shows error status.
not much detail in the netmaker log, other than "sent peer update for node"
while initiating netclient join following logged
[netclient] 2022-07-30 20:46:48 could not connect to broker broker.netmaker-test.org connect timeout [netclient] 2022-07-30 20:46:48 connection issue detected.. attempt connection with new certs and broker information [netclient] 2022-07-30 20:46:48 certificates/key saved [netclient] 2022-07-30 20:47:20 could not connect to broker at broker.netmaker-test.org:443 [netclient] 2022-07-30 20:47:20 failed to publish update for join connection timeout


07/30/2022, 9:25 PM
They don't have mq connectivity. See the mq troubleshooting gist.


07/31/2022, 10:51 AM
thanks for sharing @bored-island-21407
Here netmaker is running in aws-public-subnet and server 1 is on aws-private-net and sever2 is at home network.
communication between netmaker and server2 in home network works fine
but server1 is not able to communicate to server1 and netmaker
any suggestions on how can connectivity can be set among server 1(aws-private-network) and netmaker(aws-publi-net), server2(home network)
it's working as expected. made a mistake in configuring the security group in EC2 to open inbound port with UDP protocol as worngly mentioned it as TCP. Got that fixed, and evertything works fine. Thank you.