[Help] Login Server Console strange errors

[baiumbg]

While the server is running (there are absolutely no problems IG, or while logging in) I get this in my login server console:

 

First I get this:

Potential Flood from 94.26.20.47
GameServer (94.26.20.47): Connection lost: Connection reset
Potential Flood from 94.26.20.47

After that I get A LOT of these:

GameServer (94.26.20.47): Connection lost: Connection reset

And this from time to time:

GameServer (94.26.20.47): Connection lost: Software caused connection abort: rec
v failed

How can I fix this?

 

P.S. I use L2JServer CT2.4

[bauwbas]

When you get this error? You can login to your server or not?

 

If no, i thing you done mistake in gameserver\config\server.properties

 

_______________________________________________________________________

# Where's the Login server this gameserver should connect to

# Default: 127.0.0.1

LoginHost = 127.0.0.1

_______________________________________________________________________

 

i think you changed this ip to your own and gs server cannot connect to login server.

[baiumbg]

LoginserverHostname = *

 

Nope. Anyway, nevermind. I'm stopping the server because something went wrong and now I have to redo everything. But that's not happening. So, yeah...

[bauwbas]

Not LoginSERVERHostanme, but LoginHost

[Intrepid]

you are flooded i think its obvious

[Tryskell]

How can I fix this?

 

Ban IP, and release it anew some days after. It's stupid to let an IP banned forever, as IPs are modified each time you reboot your box (livebox, etc, etc).

 

You can add such conditions where is the "Potential Flood from" message. Instead of just logging the gameserver with "there is flood", you add actions like close connection / ban IP...

 

About releasing banned IPs, you can do it manually, or automatically via an admin command / scheduled task. But you have to program, it's clear.

 

If it's not a LIVE server (aka there aren't players on it except you), you just focked your server alone lol. Checkout anew, or correct your fixes.

 

----

 

An other way is to show it to developers via tickets system... With exact logs.