Onset Server Not Showing in List or Players Can't Connect

If your Onset server is not in the server list, check that masterlist is true in server_config.json and that the query port (game port minus one, UDP) is open. If players see it but cannot get in, the usual causes are the game port being blocked, the HTTP download port (game port minus two, TCP) being blocked so they hang while downloading packages, a password mismatch, or a package error that leaves the server half started. Each is quick to rule out with the console open.

How Onset networking works

Onset uses three ports, all worked out from the port value in server_config.json:

If you change port to 7800, the others become 7799 and 7798. Many connection problems come from forwarding the main port only.

Problem 1: The server is not in the list

1. masterlist is off. In server_config.json, set "masterlist": true and restart. With it off the server is private by design, and players have to use direct connect.
2. Query port closed. Forward the game port minus one as UDP. Without it the list cannot read the server.
3. The server did not finish starting. A JSON syntax error in server_config.json stops it reading the config at all. Check the console right after start.
4. The list itself. Onset is an old game that has not been updated in years, and its public list depends on the original developers' services. If everything on your side checks out and direct connect works, share the address and let players connect directly. That route does not depend on the list.

Problem 2: Join times out

The client never reaches the server.

• Forward the game port as UDP to the server's local IP.
• Allow OnsetServer through the firewall (Windows Firewall, ufw, firewalld).
• Make sure "ipaddress": "0.0.0.0" so the server listens on every interface. A wrong fixed IP here makes it listen on an address nobody can reach.
• Check for CGNAT: if your router's WAN IP differs from your public IP, port forwarding cannot work. The options are in how to host a game server without port forwarding.

Problem 3: Stuck downloading packages

Players connect, see the download stage, and it never finishes. This is almost always the TCP HTTP port (game port minus two). Forward it as TCP, not UDP. A very large package, such as one with big UI files or sounds, can also take a long time on slow connections, so check the package size before blaming the network.

Problem 4: Wrong password

The password value in server_config.json is case sensitive. If it contains quotes or backslashes, JSON escaping can change it from what you meant. Use a plain password with letters and numbers, restart, and test.

Problem 5: Players join but the server is broken

Players spawn in an empty world, commands do nothing, or the screen sits on a loading UI forever. That points at packages, not the network.

• Read the console from the top of the last start. A Lua error names the file and line.
• A package can fail while others keep running, so the server looks half alive.
• A roleplay framework that cannot reach its database will often fail completely. Check the MariaDB plugin is in plugins and the database details are correct.
• Remove the newest package from the packages list, restart and test. Add packages back one at a time.

The Onset package guide covers package structure and load order.

Problem 6: Server full or player limit hit early

Check maxplayers and iplimit. iplimit caps how many players can join from one IP address. If several friends play from the same house, or a group shares one network, a low iplimit turns them away even when the server has room.

A checklist to run in order

1. Console shows the server started without JSON or Lua errors.
2. masterlist is true if you want to be listed.
3. Game port UDP, query port UDP and HTTP port TCP are all forwarded.
4. Firewall allows the server.
5. Password and iplimit are what you expect.
6. Direct connect works from outside your network.

Honest note on Onset's state

Onset has had no developer updates in several years and is still in Early Access. That means no fixes are coming for bugs in the client or the list, and the community is small. Most groups still running it play by direct connect with a shared address, which works reliably.

Removing the network side

A GamezServers Onset server comes with its own address and all three ports open, so problems 1 to 3 mostly disappear. Port, name and password are written into server_config.json on every start, the live console shows package errors as they happen, and the file manager lets you fix a broken line in the browser. Questions go to support 24/7 at support@gamezservers.com. For the setup itself, see how to host an Onset server.

FAQ

Why is my Onset server not in the server list?

Either masterlist is false or the query port (game port minus one, UDP) is not reachable. Fix both and restart.

Why do Onset players get stuck downloading?

The HTTP port (game port minus two) is blocked. It needs TCP, not UDP.

Can players join an Onset server without the list?

Yes. Use direct connect with the server's IP and port. Many groups only play this way.

What does iplimit do in Onset?

It limits how many players can connect from one IP address. Raise it if friends share a network.