I used this filter on a other vps and it was here that the problem occurred when an attack occurs, the CPU raises to 100% and after that the filter is closed. Why is this happening or what can this solve the problem
the attack falls on the filter Why does the filter not protect himself from attack !
there is something strange after registering more than 50 players or less than this, after this, no one can run the server
I used this filter on a other vps and it was here that the problem occurred when an attack occurs, the CPU raises to 100% and after that the filter is closed. Why is this happening or what can this solve the problem
the attack falls on the filter Why does the filter not protect himself from attack !
I used this filter on a other vps and it was here that the problem occurred when an attack occurs, the CPU raises to 100% and after that the filter is closed. Why is this happening or what can this solve the problem
the attack falls on the filter Why does the filter not protect himself from attack !
there is something strange after registering more than 50 players or less than this, after this, no one can run the server
I'm sorry to break this to you, but no program in the world can help you against DDOS attacks.
Goodluck
I used this filter on a other vps and it was here that the problem occurred when an attack occurs, the CPU raises to 100% and after that the filter is closed. Why is this happening or what can this solve the problem
the attack falls on the filter Why does the filter not protect himself from attack !
there is something strange after registering more than 50 players or less than this, after this, no one can run the server
seems like ur using the console one if u got the source you gotta edit the protection methods , a friend of mine did that he specify the connection type and consider if it wasn't normal blocks it