hello
i have 3 nodes.
node 1 & node 2 : version 1.91.2 (running the minimal allowed version 1.24.0) → still ok
and node 3 (the lastest) with version 1.92.1 (running the minimal allowed version 1.91.2 ) : this one is OFFLINE & MISCONFIGURED
it was ok 2 hours ago
i tried to stop , rm & restart the node but noway
seems port is closed : Port [28969] is closed on 2.11.xxx.xxx
i have checked my router and it is well configured .
an idea ?
thx
1 Like
Alexey
December 8, 2023, 1:46am
2
As usual, check everything from this checklist:
It should connect in seconds. There are a few things you should check.
Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port.
If it’s closed, it could still be several things.
Make sure the WAN IP you see in your router settings matches the IP shown on the above page.
Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…
Check your logs for FATAL errors.
1 Like
Skw911
December 8, 2023, 7:57am
3
hello, i have same problem not update… stil block 1.92.1 now offline, my farm worck for 3 years no problem…
1 Like
i have 3 nodes :
xxxxxxxxxxxx:28967
xxxxxxxxxxxx:28968
xxxxxxxxxxxx:28969
ok i have checked all :
port in router; identity.cert …;
it was a wrong config in config.YAML :
public address to listen on server.address: :28969
change by # public address to listen on
server.address: :28967
and all is OK
i think that the wrong port of my bad config.yaml has been taken after the first update.
2 Likes
Alexey
December 9, 2023, 2:29am
5
You likely changed the config, but forgot to restart the service. When the update is happened, the node has been finally restarted to take this change, and you noticed a problem.
1 Like
Alexey
December 9, 2023, 2:32am
6
Hello,
you need to check everything too from the list above.
If it’s a Windows node you can use this checklist:
1 Like