Nexardo / Blog
Setup guides, diagnostics and practical decisions for running games on your own VPS.
Counter-Strike 2
Diagnosing Counter-Strike 2 Steam Server Browser visibility: resolving A2S_INFO query failures, game and query UDP port separation, iptables firewall, and packet inspection.
Read the guideCounter-Strike 2
Deploying Metamod:Source and CounterStrikeSharp on CS2 Linux server: configuring gameinfo.gi hooks, installing the .NET runtime for C# plugins, and setting admin roles in admins.json.
Read the guideCounter-Strike 2
Separate CS2 gameplay UDP, server queries and administration when configuring NAT and firewall rules.
Read the guideCounter-Strike 2
Step-by-step setup of a dedicated CS2 server on Linux: SteamCMD staging, GSLT authentication, and resilient systemd configuration.
Read the guideCounter-Strike 2
Distinguish network transit ping from sub-tick CPU processing delays in CS2: core inspection, performance governors and socket buffers.
Read the guideCounter-Strike 2
Diagnose CS2 server segmentation faults after engine patches: vanilla engine verification, updating Metamod and CounterStrikeSharp.
Read the guideCounter-Strike 2
Configure CS2 dedicated server Workshop map downloads using a Steam Web API key (-authkey) and resolve Map missing disconnects.
Read the guideCounter-Strike 2
Toggle your CS2 dedicated server between 5v5 competitive play and grenade practice drills on the fly via RCON and custom scripts.
Read the guideCounter-Strike 2
Update a Counter-Strike 2 server via SteamCMD while protecting custom game configurations and Metamod:Source hooks in gameinfo.gi.
Read the guideCounter-Strike 2
Find why a CS2 server is missing from the browser: GSLT, the game UDP port, network reachability and search filters.
Read the guideCounter-Strike 2
Trace a failed CS2 join on Linux through the public endpoint, UDP socket, two firewalls, packet arrival and game rejection.
Read the guide
