ok, but did u configured the port forward?
Dear Alex,
Yes that is correct.
On server did u activated the ufw? Also do u have another firewall? The port 6000 should be opened to accept connections from any… the public IP
Can u check here if the port 6000 is opened to accept external connections
Hello Alex,
It seems my ISP is blocking me. I contacted them and they need 24 hours to rectify the issue. I will wait until tomorrow and we will see how it goes.
Thank you very much.
1 Like
Dear Alex,
That webpage you have sent me shows everything closed but i tried telnet and port seems to be open now. But TX is still at 0.
because u are using internal/private IPs, but the other public nodes will connect to you via de public IP port 6000… did u set a port forward on your local router to map the incoming conections for port 6000 to the internal relay IP port 6000 or 6001…?
ISP forwards from all ports to my internal host IP. My VMs are configured as Bridged, so they have different IPs.
Do I need to set my VMs to NAT and then contact my ISP again to map all incoming connections for port 6000 to my VMs relay IP?
Different IPs but are private right?
So tell me how many nodes do u have?
And what are the IP and port for each node?
Basically I have one VM for Block producer (bridged) with IP X.X.242.130:6000 Then I have another VM the Relay node (bridged) with IP X.X.242.131:6000.
Then my host’s IP (windows) is in subnet X.X.2.X (private IP)
Then my ISP, port forwarded the port 6000 to my host IP X.X.2.X from the public IP (217.175.222.173)
What changes need to do?
Strange solution, I don’t understand… your outside traffic with destination 6000 should be map to ur relay private address → 6000
Understood. So for my Relay it is better to use NAT with IP X.X.2.X:6000? Same subnet as my host?
For relay… inside topology updater log u should have the relay PUblic IP… the traffic to that IP with destination port 6000 (if the relay use 6000) should be forwarded to the relay private IP to port 6000
Relay public IP 6000 → PF → Relay private IP 6000
Dear Alex,
Thats how i had my port forwarding thing. I have changed again the topology updater file and i have run it. Now i see the message you told me that i need to see.
Now i need to wait 4 hours and the TX will start counting?
perfect… now the port is open, you will not need to wait 4 hours because u already see the message glad you are staying with us… but now you should wait for other nodes to connect yours… but for this the nodes should be restarted… so it will take time…
have patience and check in glive from time to time if you see more IN peers, other nodes than your producer
Hello Alex, its been 6 hours but TX is still at 0. When I try to run the topology updater I now always get the message one request per hour.
Because it’s running automatically once/hour
Have patience, could take more hours, if not I will connect my relay to yours
Thank you so much Alex. You are very helpful and I appreciate that. I will update you tomorrow then, in 10 hours. Once again thank you so very much.
1 Like
Go to log file for topology updater… do u still see glade you’re staying with us! Right?
