[BUG] about flux HOT 9 CLOSED

It was an ISP routing problem.

from flux.

Hi @SergeRPM
Your node is not accessible from outside on the ports needed. Please ensure that ports 16126, 16127, 16128 are fully open. So other peers can connect to your node.

from flux.

Hi! Thanks for the answer.

My external ip address XXX.XXX.69.100.
All necessary ports are open and available from outside.
The Node had worked properly, but had stoped and i supose it happened after the zelflux's upgrading. The command zelbench-cli getbenchmarks returns not my ip address. Probably it is the reason.

sd@zel01-node:~$ zelbench-cli getbenchmarks
{
"ipaddress": "XXX.XXX.75.2",
"status": "failed",
"time": 1595825507,
"cores": 0,
"ram": 0,
"ssd": 0,
"hdd": 0,
"ddwrite": 0,
"eps": 0
}

Could you expain where the different ip-address from? Why it is not my?

Best regards

from flux.

Hi,
ZelBench has it's own mechanism for detecting true IP on which your node is actually accessible. The reported address from ZelBench is the accurate one and that address is used for all zel/flux purposes.
That said, Zel and flux does not really care what externalip is set in zelcash.conf file.

from flux.

ok, but i know my ip-address and it is available from outside, all ports are open, the daemon listens them.
"own mechanism for detecting true IP" detect wrong ip, where the zelcash daemon is not available.
What shall i do in this case?

from flux.

When you log into your vps and write following command what IP address do you get?

curl ipecho.net/plain

from flux.

So did you fiond a solution? Does it have to do with port forwarding?

from flux.

Hello, I have the same problem. The IP adress indicated in the benchmark is not the IP adress of my computer. @SergeRPM can you explained in details how you have resolved this issue. Thank you for your help

from flux.

It was an ISP routing problem.

I think I have the same issue, how did you manage this ISP routing problem?

from flux.