RAGE MP Server Not Showing or Stuck Downloading? Fixes

If your RAGE MP server is missing from the launcher list, check "announce": true in conf.json first, since many default configs ship with it set to false, then make sure UDP 22005 (or your game port) is reachable. If players see the server but hang on the download screen, the cause is almost always the HTTP download port, which is your game port plus one (TCP 22006 by default), or a client_packages folder that is too big. Version mismatches after a GTA V or RAGE MP update cause the rest.

Which problem do you have?

A reminder before you start: RAGE Multiplayer is an independent project with no affiliation with Rockstar Games or Take-Two. Rockstar support cannot help with it; the RAGE MP forums and Discord can.

Fix 1: Turn announce on

conf.json decides whether the server registers with the RAGE MP master list:

{
  "name": "Los Santos Late Shift",
  "announce": true,
  "port": 22005
}

With "announce": false the server runs fine but is invisible in the launcher, and only Direct Connect works. That is a reasonable setting while you build a gamemode, and an easy one to forget on launch day. Change it, save, restart.

While you are in there, check the JSON is valid. A trailing comma or a missing quote stops the server from starting at all, which also makes it "not show up." The server console prints the parse error.

Fix 2: Make the game port reachable

The master list and every player need to reach your game port over UDP (22005 by default).

• On a home server, forward UDP 22005 to the server PC and allow it in the firewall.
• If you changed port in conf.json, forward the new number and give players the new address.
• "bind" should be 0.0.0.0 unless you know you need a specific IP. Binding to 127.0.0.1 makes the server reachable only from itself.

Test with a friend on another network using Direct Connect with your public IP and port. If that times out, the port is the problem, not the master list. Friends cannot connect but I can walks through the router checks, and how to tell if you are behind CGNAT covers connections where forwarding cannot work.

Fix 3: Open the download port

When a player connects, the server sends everything in client_packages over a small built in HTTP server. That server listens on TCP at the game port plus one:

If the download port is closed, players connect, see the download screen, and sit there. Forward and allow the TCP port as well as the UDP one. On a host where you cannot open ports yourself, ask support to confirm that the port above your game port is open for TCP.

Fix 4: Shrink client_packages

Every player downloads the whole client_packages folder on first join, and again whenever files change. A 300 MB folder of uncompressed images, fonts, sounds and custom vehicle files takes a long time on slower connections and looks exactly like a stuck download.

• Compress images and audio.
• Remove unused fonts, source maps, test files and editor leftovers.
• Split large optional assets so only what is needed ships.
• Keep custom vehicles and clothing to what the server actually uses.

The resources-compression-level option in conf.json controls how hard the server compresses packages for download. Higher levels save bandwidth at the cost of some CPU, which suits a public server with many joins.

If downloads complete for some players and not others, ask the stuck ones to check that antivirus or a VPN is not blocking the RAGE MP launcher.

Fix 5: Versions

Three versions have to line up:

1. GTA V. After a Rockstar update, RAGE MP itself usually needs an update before it works with the new game build. Players see errors or crashes until then. Wait for the RAGE MP update and let the launcher install it.
2. RAGE MP client and server. A server on an older release can reject current clients. Download the current server files and restart.
3. Your gamemode. Scripts written against older RAGE MP APIs can fail after a server update. The console shows the errors.

Since RAGE MP supports both the Legacy and Enhanced editions of GTA V, a mixed group can play together, with one exception the RAGE MP team points out: if you replace advanced game files such as gameconfig.xml, Enhanced players need versions rebased for that edition in client_packages/game_resources_g9.

Fix 6: Joins, then crashes

When the download completes and the game crashes or goes black, the problem is usually in what you ship to the client: a broken client script, a missing file in a require, or a custom asset that does not suit the player's GTA V edition. Test with a clean client_packages that only contains a tiny index.js. If that joins fine, add your resources back one at a time.

Quick checklist

The hosted route

A GamezServers RAGE MP server runs on its own address with always on DDoS protection, which matters for public roleplay servers. The server name is set in the control panel and written into conf.json on start, and the rest of the file, including announce, is yours to edit in the file manager. The live console shows the master list registration and every script error as the server boots, and support is on email at support@gamezservers.com if you need a port checked.

FAQ

Why is my RAGE MP server not in the server list?

announce is false in conf.json, or the game port is not reachable. Set it to true, open UDP 22005 and restart.

Why are players stuck downloading on my RAGE MP server?

The TCP download port (game port plus one) is closed, or client_packages is very large.

What ports does RAGE MP need?

UDP 22005 for the game and TCP 22006 for downloads by default. If you change the game port, the download port moves with it.

Can players join by IP if the server is not announced?

Yes. Use Direct Connect in the RAGE MP launcher with the IP and port.