{ “resultcode”: “403”, “datetime”:“2021-02-24 20:25:12”, “clientIp”: “x,x,x,x”, “iptype”: 4, “msg”: “glad you want to stay with us, but please check and enable your IP:port reachability” }
Open the ports in fw to allow connections from public relays
1 Like
All my relays are setup for my private IPS
Do I need to add my relays publics ips? my topologyUpdater.sh is setup with private ips
No man, other public relays need to connect to ur relays… open the port in fw to accept incoming connection
sudo ufw allow proto tcp from any to any port 6000
2 Likes
Set what port?
sudo ufw allow proto tcp from any to any port 6000
Skipping adding existing rule
Tell me ur relays IP (public)
Or check on this site… should be opened…
sayings it closed, im using AMAZON AWS should i add it there?
Yes, open also the port in amazon firewall
Okay its showing open now
topologyUpdater.sh
{ “resultcode”: “504”, “datetime”:“2021-02-24 20:46:03”, “clientIp”: “x.x.x.x”, “iptype”: 4, “msg”: “one request per hour please” }
Great, next time should become online right? How many times it rans with nice to met u message?
O u already have the message glade u are staying with us…
it ran with the nice meet you message when I had a different topologyUpdater file. I got the better version of the topology file and hasnt done it yet.
Starting to look good
1 Like
WOAH finally some good news 
Do you know why teh other one isnt working?
Check the topology updater log message
{ “resultcode”: “201”, “datetime”:“2021-02-24 18:17:30”, “clientIp”: “x”, “iptype”: 4, “msg”: “nice to meet you” }
{ “resultcode”: “504”, “datetime”:“2021-02-24 18:22:15”, “clientIp”: “x”, “iptype”: 4, “msg”: “one request per hour please” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 18:54:25”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 18:56:22”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:02:01”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:02:49”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:04:43”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:05:37”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:06:06”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:06:25”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:06:44”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:07:15”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:08:49”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:09:30”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:11:28”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:14:57”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:15:22”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:15:39”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:16:08”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:16:49”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:17:23”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:21:26”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:22:09”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:22:33”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:23:15”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:23:25”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “502”, “datetime”:“2021-02-24 19:23:52”, “clientIp”: “x”, “msg”: “invalid blockNo ” }
{ “resultcode”: “203”, “datetime”:“2021-02-24 19:24:49”, “clientIp”: “x”, “iptype”: 4, “msg”: “welcome to the topology” }
It’s not the same issue like first one?
./topologyUpdater.sh
{ “resultcode”: “403”, “datetime”:“2021-02-24 21:35:06”, “clientIp”: “x”, “iptype”: 4, “msg”: “glad you want to stay with us, but please check and enable your IP:port reachability” }