Plugin Author
NilsD
(@nilsdberlin)
The update has been released and should work now, though it might take up to 6 hours for it to become available to you.
Plugin Author
NilsD
(@nilsdberlin)
Sorry for answering here late — we sorted this out over Discord in the meantime, and it turned out to be worth the trouble: it wasn’t one problem but three, and two of them were bugs in the plugin.
What it was in this case: the web hosting running the WordPress site did not allow outgoing connections on unusual ports. Steam games, Bedrock and Call of Duty are queried over UDP, Minecraft Java over TCP — if the host only allows ports 80, 443 and DNS, none of them can ever answer, no matter what you enter. The game servers themselves were perfectly fine the whole time.
What changed in the plugin because of this report (1.0.4 – 1.0.8):
- A “Test connection” button when you add or edit a server. It tries the protocols and the usual ports by itself and fills in what actually answered — useful because Steam games answer on a separate query port, while CS2 answers on the game port itself. Getting that wrong is the most common cause of “shows offline”.
- When a query fails, administrators now see the reason on the card and in the server list, instead of a bare “offline”.
- Diagnostics now checks whether your site may send UDP at all — and tells apart “UDP works” from “only DNS gets through”, which looks identical from the outside but means nothing can ever be queried.
- Fixed: Minecraft addresses using an SRV record were never resolved. Most hosters hand out a short address without a port and redirect behind the scenes — those servers showed as offline although players could join fine.
- Fixed: server names on Quake 3 engine games showed leftover colour codes.
So if your server shows offline: update to 1.0.8, open Game Server → Diagnostics, and check the “Outgoing UDP” line. If it says anything other than available, it’s your web host, not your game server — and the wording matters when you ask them: it’s about outgoing connections from your website, not about opening ports on it.
Thanks to @smolf for reporting it and for testing patiently. Genuinely useful — I’d never have found either bug on my own servers.
