This find could (maybe) save someone few hours spent on trying to figure out why their node is OFFLINE when you specified different port than DEFAULT listening port.
- checked firewall (even disabled for testing) - it should work fine - other applications work
- you set up port forwarding on your router (it is OK), even turned off firewall - other applications work
- You check your other ports with online port checker https://www.yougetsignal.com/tools/open-ports/?port=28967(insert your port)
One of the solutions that might be keeping you OFFLINE
Well… check config.yaml file - It happened to me twice now - when I installed the node via windows GUI client ( and Debian docker) and specified DIFFERENT listening port --> this change DOESN’T propagate to config file.
When you run it, it still uses DEFAULT listening port, you have to edit the config.yaml file to correct the port number.
Then rm node and reacreate it (for docker users) or just restart service for windows GUI users.