Reading the Graphs and Attack History
A normal server shows a steady allowed line that follows your player count and a blocked line near zero with occasional small blips (internet background noise, scanners, stray queries).
An attack shows as a sharp rise on the blocked line while the allowed line stays flat. That is the correct picture: the flood arrived, GlitchGuard dropped it, your players did not notice. The breakdown under the graph tells you what kind it was.
If the allowed line also rises sharply and your server struggles, the traffic is getting through a rule you have allowed. Usually this means a UDP port on Rate limited where a protocol filter would be stricter, or a flood of real-looking connections that under-attack mode would cap. Turn on under-attack mode, then review the filter on the affected port.
Attack history lists each event with its peak rate, duration, packets dropped and type. Useful for support tickets and for spotting patterns (same time each evening, for example). Each attack also triggers a Discord message if you have set a webhook.
Common Problems
My game server stopped working after I enabled GlitchGuard or changed rules
The port is not in your rules table. Anything not listed is dropped. Find the port your server uses (see ports and filters), add it with the right protocol and filter, save, wait a few seconds and try again. Check both TCP and UDP if the game uses both.
Players can connect directly but the server does not show in the server browser
The query port is missing or has the wrong filter. Add the query port as UDP with Steam query only (or Steam query + game if it shares the game port), then save.
The website works but the game does not, or the other way round
Websites are TCP, most games are UDP. You have one and not the other. Add the missing protocol row.
I cannot SSH or Remote Desktop in
The SSH or Remote Desktop service is not enabled. Under Add service, turn it on and save.
Ping does not respond
Ping is turned off in your rules. Add the Ping service. Ping failing while everything else works is harmless, and sometimes deliberate.
My VPN will not connect
Check the port and protocol match your VPN config (WireGuard default UDP 51820, OpenVPN default UDP 1194). Check you have not applied the WireGuard filter to an OpenVPN port or the other way round. If you run OpenVPN in TCP mode, add TCP 1194 as well.
TeamSpeak file transfers or ServerQuery do not work
Those are TCP 30033 and TCP 10011. The TeamSpeak preset adds both; if you removed them, add them back.
RCON or an admin tool does not connect
RCON ports are TCP and separate from the game port. Add it as TCP.
Players report lag or high ping
GlitchGuard filtering happens in microseconds and does not add measurable latency. Check whether under-attack mode is on; it caps new connections and can make joining a busy server slower. Check the traffic graph: if the allowed line is spiking, the server itself may be overloaded. If a UDP game port is set to Rate limited and you have a very large player count, open a ticket and we can review the preset's thresholds for your server.
"Please wait 5 minutes between changes"
A minimum interval between saves. Wait and save again.
"Rules could not be read; please reload the page"
The browser session expired or the page was open for a long time. Reload the service page and redo the change.
Under-attack mode turned itself on
Automatic mode detected an attack. Check Attack history and your Discord channel for the details. It will turn itself off 30 minutes after the attack ends. If you would rather it never did this, turn Automatic off.
My IP address changed (migration, reinstall)
Protection follows the IP on your service. Our systems re-check daily and move protection automatically. If you need it moved immediately, open a ticket.
Discord alerts are not arriving
The URL must start with https://discord.com/api/webhooks/ and the webhook must still exist in Discord (deleting the channel deletes the webhook). Paste it again and save.
I am still being attacked and the server is suffering
Turn on under-attack mode. Note the time and open a ticket quoting your IP; the attack history and graphs give us what we need to tune your filters or thresholds.
Good Practice
- Open only what you use. Every closed port is one that cannot be attacked.
- Prefer a protocol filter over Rate limited whenever your protocol is supported.
- Keep Ping on unless you have a reason to hide the server; uptime monitors need it.
- Set a Discord webhook. Knowing an attack happened, and that it was absorbed, is most of the value.
- Leave Automatic under-attack mode on.
- After any change, test every service you run, not just the one you changed.
Frequently Asked Questions
Next Steps
If the problem is a missing or wrong port, the ports and filters guide has the quick reference for common servers. For the panel itself, see the setup guide. Still stuck? Contact us or open a ticket from your service page.
Not protected yet?
GlitchGuard is available as an add-on on VPS and dedicated servers. Open a ticket from your service page and we will switch it on, then come back to this guide.