Troubleshooting: server browser N/A + blank description#45
Merged
Conversation
Add an entry for the 'my server shows N/A and blank in the in-game
browser' confusion. Operator data we collected over an evening:
- sudo ss -tulnp | grep ':269' shows ports 26900 + 26902 bound,
but never 26901 or 26903.
- Server log shows successful EOS init, EOS registration with 56
attributes, AND Steamworks GameServer.Init + GameServer.LogOn.
- Same pattern reproduces on two unrelated boxes (Hetzner Linux
+ WSL Linux), and the symptom hits a subset of OTHER operators'
servers in the browser too — not unique to KC.
So 7D2D V 2.x has moved server browser discovery to EOS. Steam Query
ports 26901/26903 not binding is by design, not a regression. The
N/A + blank display is something downstream of EOS (lookup miss or
client-rendering bug), and not fixable from the server side.
Entry calls out what we *confirmed* (logs + ss output we have) vs
what we *inferred* (the EOS-downstream bit), so the next operator
googling 'server browser N/A' gets the actual mechanism instead of
chasing a phantom Steam Query bind.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Captures tonight's debugging detour into one entry so neither of us re-derives it next time.
What this is
Operators see their server appear in the in-game browser with
N/Aping and an empty description. Server is otherwise fine — direct-IP connect works, KC's panel dashboard shows real stats. Confused us for a couple of hours.What I learned (the actual mechanism)
7D2D V 2.x switched server-browser discovery from Steam Query to EOS. Steam-side ports `26901` / `26903` are not bound by the dedicated server anymore, by design. The server logs literally say:
```
[Platform] Using cross platform: EOS
[EOS] Server registered, session: , 56 attributes
[Steamworks.NET] GameServer.Init successful
[Steamworks.NET] GameServer.LogOn successful, SteamID=...
```
So the server is published, with description / world / player count bundled into the EOS session attributes. The `N/A` + blank display is something downstream of EOS — affects a subset of operators' servers across multiple unrelated boxes, comes and goes.
What's confirmed vs inferred
The entry frames it that way explicitly:
I deliberately don't claim "this is a vanilla bug in b14" or "your client is broken" — we tried both as theories and couldn't fully verify either. The entry just tells the next person: don't chase a missing 26901 bind, the server is fine.
Test plan
🤖 Generated with Claude Code