You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 12, 2023. It is now read-only.
I am getting a lot of 'failed to dial challenger' errors while sending witness proof with a direct p2p connection to the challenger. This causes a lot of beacons with 0 witnesses since the miners cannot connect to the challengers. Consider logs from my three miners:
My networking setup is correct - ports are properly forwarded, no firewall is blocking the inbound/outbound traffic. I also run them behind a VPS with separate public IPs for each one of them because of helium/erlang-libp2p#44. This way it yields much more witnesses but there are still cases where direct p2p connection fails (timeouts) for an unknown reason.
I think these failures happen way too often to be an occasional issue with the other peer (challenger) it seems to me that this is related to the network itself.
Maybe there should be an additional logic if p2p connection timeouts so that the witness proof is relayed anyway.
The text was updated successfully, but these errors were encountered:
I am getting a lot of 'failed to dial challenger' errors while sending witness proof with a direct p2p connection to the challenger. This causes a lot of beacons with 0 witnesses since the miners cannot connect to the challengers. Consider logs from my three miners:
https://pastebin.com/j2Q6XfPv - miner 1
https://pastebin.com/EAQYYxQA - miner 2
https://pastebin.com/Vzyuvdvy - miner 3
My networking setup is correct - ports are properly forwarded, no firewall is blocking the inbound/outbound traffic. I also run them behind a VPS with separate public IPs for each one of them because of helium/erlang-libp2p#44. This way it yields much more witnesses but there are still cases where direct p2p connection fails (timeouts) for an unknown reason.
I think these failures happen way too often to be an occasional issue with the other peer (challenger) it seems to me that this is related to the network itself.
Maybe there should be an additional logic if p2p connection timeouts so that the witness proof is relayed anyway.
The text was updated successfully, but these errors were encountered: