IP Banned; Port Forwarding

SemkoDev / field.cli

WE HAVE MOVED TO A NEW REPOSITORY

https://gitlab.com/semkodev/field.cli

ISC License

34 stars 7 forks source link

IP Banned; Port Forwarding #31

Open Kwintspiracy opened 6 years ago

Kwintspiracy commented 6 years ago

Hey all,

I'm having 2 issues:

Can't seems to find any neighbours
and have my IP banned: Fri Mar 23 2018 23:16:43 GMT+0800 (+08) field: Field update error to field.carriota.com: 429 null {"error":"IP flagged for 5 minutes due to misbehaviour: Ping back to Client IP failed: XXX.XXX.XX.XX"}

I guess both are related, so I might have missed something in the port-forward step as I'm being a bit unsure with how to set this up exactly. I usually use redirection, not familiar with forwarding. Here are my router settings. Does that look correct to you. The IP being the local machine running the Node. capture d ecran 2018-03-23 a 11 16 28 pm

Thanks for your help

romansemko commented 6 years ago

Can you please check the port of your node is open? https://www.yougetsignal.com/tools/open-ports/

Kwintspiracy commented 6 years ago

My TCP ports que correctly opened but my UDP is closed...strange since its setup the same way.

New-older commented 6 years ago

I guess you have a Dynamic WAN IP, you should use DDNS, Noip.com is a good choice, you can also search Ngrok or Frp on github, that is a tunnel.

mateuszseczkowski commented 6 years ago

Anyone with a solution? I have the same problem and it occurred yesterday, after a week of trouble-free work. Currently it works for a while without any problem and then, after few minutes the problem comes back... Weird behaviour.

~~My node https://tangletools.org/field/iotapolandnode_ms1. All required ports are correctly opened~~

Found the solution on Discord channel. IoTMOD - wrote:

Ok, try to use an addresses instead of the seed. If there are a lot (threshold depends on your node's specs) of used addresses on your seed, field fails to find an unused address. Because field checks this every 20 seconds it can't response to the load balancer then. I already reported this to Roman some weeks ago.

NEW seed would also help :)