Is This Game Down
You can fix thisConfirmed

Dragonwilds server not showing up (version mismatch fix)

A dedicated server you (or a friend) started for RuneScape: Dragonwilds doesn't appear in the Public tab of the Worlds screen, even though the server itself is running and other games' dedicated servers show up fine on the same box.

Also appears as: dragonwilds server not showing up, dragonwilds dedicated server not appearing, cant find my dragonwilds server, dragonwilds server not in list, dragonwilds server browser empty, dragonwilds world not showing up

This is on your end, not Jagex's, but it's one of the best-documented issues in Dragonwilds: a server that's running fine can still fail to show up in the Public tab. The usual causes are a server/client version mismatch, a Steam privacy setting, the case-sensitive world-name search, or a missing OwnerID.

Multiple third-party hosting companies (Nodecraft, GameServerKings, XGamingServer) independently document it, and Jagex's own "Dedicated Servers" guide and Known Issues page confirm those causes. A separate, easily-confused issue: Jagex's Known Issues page says joining via a Steam Invite "doesn't currently connect as intended," which looks like a broken server but isn't.

If none of the documented causes apply, the server may simply not have finished booting — check its startup logs and firewall ports as a last resort.

Fix it, step by step

  1. Restart the dedicated server so its version matches your client

    Restart the dedicated server so it's running the same version as your game client. Jagex's guide says that if you can't see your server any more, "use the logs to ensure that the version it runs matches the one your game does", which is "likely to happen any time an update or hotfix is released". The server's version is at the top of its logs; your game's version is in the top left corner of the game. "Shockbyte servers just need to restart to update automatically", and the latest patch notes (1.0.1.2, October 23, 2026) say "Dedicated Servers will need to be restarted to apply the hotfix".

  2. Check your Steam account/session privacy is not set to Private

    Check that your Steam account/session privacy isn't set to Private. Jagex's Known Issues page states this "will completely hide all hosted sessions in the server list, and sessions hosted by friends" — independent of anything wrong with the server itself.

  3. Search the Public tab for the exact, case-sensitive world name

    Search for the exact, case-sensitive world name in the Public tab rather than an approximation — Jagex's guide confirms the search is case-sensitive.

  4. Fill in the OwnerID field in the server config with your Player ID

    Confirm the OwnerID field in the server config is filled in with your correct in-game Player ID (copied from the bottom of the Settings menu). Jagex's guide lists it as mandatory: "The server will not start without your owner ID."

  5. Use Public tab search instead of a Steam invite

    If you were trying to join via a Steam invite rather than searching by world name, that path is a documented limitation, not a broken server — Jagex's Known Issues page says Steam invites to a dedicated server "doesn't currently connect as intended." Use the Public tab search instead.

  6. Check the server logs and forward its UDP ports (7777 by default)

    If the server still isn't listed, check its boot/console logs for a startup error, and confirm the server's ports are reachable. Jagex's guide says dedicated servers use port 7777 by default (a second server uses 7778, and so on), and your firewall, router and ISP "must forward those ports for UDP".

Hit this error? Leave a comment

Say where you are, what you see on screen, and whether any fix worked for you.

No links. Anonymous, no account. Keep it about the game.

What people are saying

Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.

  • Nothing reported here yet.