Skip to content

Reject wildcards and malformed addresses as direct_ip - #2619

Merged
niklaswa merged 1 commit into
masterfrom
validate-direct-ip
Oct 11, 2026
Merged

niklaswa merged 1 commit into
masterfrom
validate-direct-ip

Conversation

@niklaswa

Copy link
Copy Markdown
Member

A direct_ip like %.pixelhide.net passed the validation with only a misleading "could be offline" note.

  • direct_ip has to be a plain domain or IPv4 address, optionally with a port. A wildcard gets its own hint that it belongs into server_wildcards, everything else (https://, paths, spaces, no dot) a generic one
  • An invalid address skips the server status check, so there is no offline note anymore
  • Every wildcard needs a domain after %., invalid ones are no longer compared against the server
  • The docs describe direct_ip as the address players join, without wildcards

Tested against the manifest of #2617 and a set of broken addresses. Every direct_ip and wildcard on master matches the new format, so existing entries do not start failing. The manifest image builds and runs with the dependency versions bumped in #2615 and #2616.


Token stats: 63,872,373 tokens, $24.61
Tokens
Input (uncached) 338
Cache write 999,641
Cache read 62,668,561
Output 203,833
Total 63,872,373

169 requests, 0 subagents. Cost at API list prices: claude-opus-5-5 $24.61

A direct_ip like %.pixelhide.net passed with only a misleading offline note.
The direct IP and every wildcard now have to be a plain domain or IPv4
address, optionally with a port, and an invalid address skips the server
status check.
@niklaswa
niklaswa merged commit 64e7838 into master Oct 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant