Introduction

This short tutorial will show you how to run a RageMP server on Linux distributions.

By default, RageMP makes use of port 22005 UDP for server access so make sure that it is unblocked before starting your server

Windows

Troubleshooting

Linux

Installing GCC 6

Debian, Ubuntu, and derivatives

Ubuntu 16.04

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install gcc-6 g++-6

Installing the server

Debian, Ubuntu, and derivatives

# Downloading server
cd /tmp
wget https://cdn.rage.mp/lin/server
mkdir ~/ragemp_server
mv server ~/ragemp_server
cd ~/ragemp_server 
chmod +x server
./server

# Firewall commands (iptables only) (dont forget to save the rule after adding it)
iptables -A INPUT -p udp --dport 22005 -j ACCEPT

CentOS 7, Fedora 19 (and later), and derivatives

# Downloading server
cd /tmp
wget https://cdn.rage.mp/lin/server
mkdir ~/ragemp_server
mv server ~/ragemp_server
cd ~/ragemp_server 
chmod +x server
./server

# Firewall commands (iptables only) (dont forget to save the rule after adding it)
iptables -A INPUT -p udp --dport 22005 -j ACCEPT

Setting up

Installing screen

For running the server in background, we recommend using screen mainly for its ease of use

Debian based (Ubuntu & derivatives)

sudo apt-get install screen

CentOS 6.x/7.x

yum install screen

Starting the server

screen -dmS RAGEMPSERVER -L bash -c 'cd ~/ragemp_server && ./server' &

# Parameter explanation
# screen -dmS = starts a separate shell without directly opening an interface towards it (detached mode). The S param defines a session name for the newly created session, so that it is easier to manage in the future.
# screen -L = basically logs whatever error that is shown by the server through the separate shell into a file for easier reference in the future.
# !IMPORTANT!
# Log output will be saved as screenlog._number_ in the server directory.
# &: IS IMPORTANT IF YOU WANT TO TERMINATE THE PROCESS GRACEFULLY

Stopping the server

To stop the server, there's usually two ways to do that, one that we call a graceful shutdown that sends the server a signal for termination and the other, well, a crash since it does not allow the code to run through the termination process correctly.

RECOMMENDED:

kill $(ps h --ppid $(screen -ls | grep RAGEMPSERVER | cut -d. -f1) -o pid)

NOT RECOMMENDED: It does not shut down the server gracefully

screen -S RAGEMPSERVER -X quit