|Esta es una traducción en progreso.|
El contenido y el formato de esta página pueden variar durante las próximas horas o días.
|Este artículo es un trabajo en progreso.|
El contenido y el formato de esta página pueden cambiar drásticamente durante las próximas horas o días.
Por favor ayuda a pagina de discusión puede contener sugerencias.si puedes. La
Por favor ayuda a si puedes. La pagina de discusión puede contener sugerencias.
This page discusses the installation and configuration of a dedicated ARK server. Refer to Dedicated Server Providers for a list of providers that rent ready-to-use servers.
For scripts that you can run on your own dedicated server, see Dedicated Server Scripts.
- 1 Prerequisites
- 2 Hardware
- 3 Network
- 4 Prerequisites
- 5 SteamCMD
- 6 Server Installation
- 7 Port Forwarding and Firewall
- 8 Automatic Startup
- 9 Updating
- 10 Console Commands
- 11 Backing Up Server Data
- 12 Troubleshooting
- 13 Tool - ARK Server Organizer
- 14 Notes
- 15 References
- 16 External Links
Prerequisites[editar | editar código]
Your OS must be a 64-bit OS (ShooterGameServer is a 64-bit executable and as such will not run on a 32-bit install of Ubuntu or Windows). The server has been tested on Ubuntu 14.04 and should also support any Windows host where the prerequisites found in
_CommonRedist can be installed.
Hardware[editar | editar código]
The server requires at least 6GB of RAM to start. Memory requirements increase as the number of connected players increases. On Windows Server 2012 R2, the client uses 2.3GB of RAM without any clients. On Linux, the installation uses 3.2GB of RAM without any clients.
Network[editar | editar código]
The server listens for incoming connections on the ports listed below. Ensure your network configuration allows incoming connections to these ports and directs them to the host that will be running your dedicated server.
|UDP 27015||Query port for Steam's server browser|
|UDP 7777||Game client port|
|UDP 7778||Raw UDP socket port (always Game client port +1)|
|TCP 27020||RCON for remote console server access (optional)|
You can host multiple dedicated servers on the same host, however be aware that CPU and memory should be monitored carefully if they are busy servers rather than test servers.
|Server instance||Game port||Raw UDP port||Query port||RCON port|
|Server game instance 1||7777||7778||27015||27020|
|Server game instance 2||7779||7780||27016||27021|
|Server game instance 3||7781||7782||27017||27022|
|Server game instance 4
completely different ports
Query Port cannot be between 27020 and 27050 due to Steam using those ports.
Prerequisites[editar | editar código]
Windows[editar | editar código]
Microsoft Visual C++ 2013 Redistributable (can be found in the Steam Ark game folder under _CommonRedist/vcredist/folder).
DirectX (DXSETUP, can be found in the Steam Ark game folder under _CommonRedist/DirectX/June2010/ folder).
Linux[editar | editar código]
64bit Linux servers will require 32 bit binaries to install/run steamcmd.
sudo apt-get install lib32gcc1
The game server requires glibc 2.14 or greater. Ubuntu 14.04 (and newer) and Debian 8 (Jessie) satisfy this requirement automatically, but older versions, such as Debian 7 (Wheezy), do not. To install the required version of glibc on a Debian 7 (Wheezy) host:
- Add the following lines to
# Experimental/unstable (sid) repositories deb http://ftp.debian.org/debian experimental main deb http://ftp.debian.org/debian sid main
- To update the host's available packages list and install the updated glibc library package, run the following commands via sudo or a root shell:
apt-get update apt-get -t experimental install libc6-dev
Note: this procedure does not upgrade the host to Debian Unstable (sid); only glibc itself and any packages it depends upon are updated.
For other older distributions that don't include glibc 2.14 or newer, refer to the distribution's documentation and support forums for guidance.
Open Files Limit[editar | editar código]
- Note: This section doesn't apply if you'll be using systemd to launch the dedicated server (as described below in #Automatic Startup), as it can set this limit at runtime.
To ensure that the host's open files limit is high enough to support the game server:
- Add the following lines to
then run the following command via sudo or a root shell to apply the change:
$ sysctl -p /etc/sysctl.conf
- Add the following lines to
* soft nofile 1000000 * hard nofile 1000000
- Add the following line to
session required pam_limits.so
Warning: Without these changes, the game server may not successfully launch. If the server appears to start, but uses a high amount of CPU time without using at least 5.5GB of RAM, it hasn't been able to open all the files it needs and the above change should be applied.
is a daemon that monitors the use of system components and dynamically tunes system settings, currently only on RHEL7, CentOS7.x, and Fedora.
Note: You need to set tuned to „throughput-performance“. Otherwise all changes in /etc/security/limits.conf will ignored!
SteamCMD[editar | editar código]
The dedicated server is available for both Linux and Windows platforms. For both platforms, SteamCMD is used to download the server files. Refer to that page for detailed instructions on its installation and usage; the instructions included in the steps below are deliberately concise for space considerations.
Warning: [Linux-specific | Windows: report missing] If you want to use a SSD to run the server, but your normal steam folder is on your main HDD, check the soft-links of the folders located in '.steam'
Server Installation[editar | editar código]
- Install SteamCMD on your host.
- Create a folder to house the server files on a volume with at least 15GB of free disk space. The server files consume about 7.5GB of space (Sep 2016), but it's wise to plan for saves and future content updates which will consume additional space.
- Launch SteamCMD on your host and use it to download the server files. (Remove the < > and replace them with double quotes, for example, force_install_dir "C:\Program Files (x86)\Ark Server")
Use app id 376030 for Survival Evolved or use 445400 for Survival of The Fittest
Steam> login anonymous Steam> force_install_dir <install_dir> Steam> app_update 376030 validate Steam> exit
- OR, run from command line:
steamcmd +login anonymous +force_install_dir <install_dir> +app_update 376030 +quit</install_dir>
<install_dir>with the full path to the folder created in Step 2. On Linux, this will be a path like
/home/steam/servers/ark. On Windows, this will be a path like
Create a script to launch the server with your desired options and settings. For simplicity's sake, place it in the same folder where the server files were downloaded. On Windows, this is a batch file; on Linux, this is a shell script. Examples are provided below. For both platforms, the server options are specified with the same basic syntax.
For Windows, create
start_server.bat: and place it in YOUR_ARK_SERVER_FOLDER/ShooterGame/Binaries/Win64/ (remove the '<' '>' symbols!)
start ShooterGameServer.exe TheIsland?listen?SessionName=<server_name>?ServerPassword=<join_password>?ServerAdminPassword=<admin_password>?Port=<port>?QueryPort=<query_port>?MaxPlayers=<max_players> exit </max_players></query_port></port>
For Linux, create
server_start.sh: (remove the '<' '>' symbols!)
#! /bin/bash ./ShooterGameServer TheIsland?listen?SessionName=<server_name>?ServerPassword=<join_password>?ServerAdminPassword=<admin_password> -server -log
On Linux, after creating the script, make it executable:
$ chmod +x server_start.sh
In both of these examples, replace
<server_name>with the desired name for your server,
<join_password>with whatever password players must provide to join your server and
<admin_password>with the password that must be provided to gain administrator access to the server. If no player join password is desired, remove the entire option from the list (including the
- Finally, to launch the server, run the script created in the previous step.
Port Forwarding and Firewall[editar | editar código]
For your server to become visible in both the Ark server lists and the Steam lists, do the following:
Windows (Firewall and Allow Rules)[editar | editar código]
- If you're on Windows 10, click on the search box in the lower left corner and type in "Firewall". Click on "Windows Firewall".
- Once Firewall opens, click "Advanced settings" on the left panel.
- Click "Inbound Rules" on the left panel, then click "New Rule..." on the right panel.
- When the New Inbound Rule Wizard opens up, select Port, then next.
- The setup will now ask you if you want to allow TCP or UDP, and what port it will be. Select TCP. Then, make sure you have "Specific local ports" selected and then put the port you plan to forward into the box (default 27020 for RCON).
- Select "Allow the connection", and continue with the wizard.
- Make sure all of the boxes are selected for where the rule applies.
- Enter a name (required) and a description (optional).
- Repeat these steps, but instead of allowing TCP allow UDP. Make sure to enter your steam browser/query port (27015 default) and game port (7777 default). You also need the raw udp socket port (7778 default, always your game port +1) if using ?bRawSockets.
- You should have 3 port rules now in the Inbound Rules section.
- This section and the port forwarding section go hand in hand.
- Close the advanced firewall window, and open Windows Firewall again.
- Click "Allow an app or feature through Windows Firewall". Scroll down to ShooterGame. Make sure all apps named ShooterGame have the Private and Public boxes checked.
- You're done, and if your ports don't work when you forward them, you can edit your Firewall inbound rules by going back to the advanced tab, selecting the Inbound Rules tab, right-clicking the rules you created, then clicking properties.
OS X (firewall application)[editar | editar código]
Linux[editar | editar código]
For most Linux distros, if there is a firewall at all it will be iptables based. Most modern distributions will use a different interface, it's a good idea to use that instead of direct iptables commands.
All firewall changes must be made either as root or with sudo. These open ports 7777 7778 and 27015 for UDP and optionally 27020 for TCP. You may want to adjust the list of ports you need by editing the "for port in..." line.
UFW[editar | editar código]
This script will open the ports in a way that will persist across reboots. UFW is the firewall on Ubuntu
#!/bin/sh if [[ $EUID -ne 0 ]]; then echo "This must be run as root" exit 1 fi for port in 7777 7778 27015; do ufw allow $port/udp done #Uncomment the next if you want to open the default rcon port #ufw allow 27020/tcp
FirewallD[editar | editar código]
This script will open the ports in a way that will persist across reboots. FirewallD is the firewall on RHEL7, CentOS7.x, and Fedora.
#!/bin/sh if [[ $EUID -ne 0 ]]; then echo "This must be run as root" exit 1 fi for port in 7777 7778 27015; do firewall-cmd --permanent --add-port $port/udp done #Uncomment the next if you want to open the default rcon port #firewall-cmd --permanent --add-port 27020/tcp firewall-cmd --reload
iptables[editar | editar código]
Keep in mind that this is only a temporary solution, and should only be used if neither of the other scripts apply for your system. To make it safe for reboots see the documentation of your distribution, how to add firewall ports to the existing configuration files - or how to add scripts to the boot process.
#!/bin/sh if [[ $EUID -ne 0 ]]; then echo "This must be run as root" exit 1 fi for port in 7777 7778 27015; do iptables -t filter -I INPUT -p udp --dport $port -j ACCEPT done #Uncomment the next if you want to open the default rcon port #iptables -t filter -I INPUT -p tcp --dport 27020 -j ACCEPT
Port Forwarding[editar | editar código]
There are many websites with tutorials on port forwarding. It is highly suggested you visit portforward.com, which offers tutorials for the majority of routers.
What ports work depends on you. Try forwarding 27015 as the port, and 27016 as the query port. 27015, 27016, and 7777 are the most common ports that work.
You MUST forward both TCP and UDP for your server to show up on any lists. You can make sure your ports are open by using the tool from portforward.com, that is, after you
Enter the ports that you have forwarded in the start_server.bat file you should have created earlier. For example,
start ShooterGameServer.exe TheIsland?listen?SessionName=<server_name>?ServerPassword=<join_password>?ServerAdminPassword=<admin_password>?Port=7777?QueryPort=27015?MaxPlayers=<max_players></max_players>
Good luck, port forwarding is not very easy.
Finding Your Server in Lists[editar | editar código]
You can access your server via the Steam servers list or the Ark unofficial list. Just search for you name in the Ark list, or find your IP address in the Steam server list.
Automatic Startup[editar | editar código]
Windows (via Scheduled Task)[editar | editar código]
You can configure a scheduled task to automatically run a batch file and start the dedicated server when the system boots.
- Open 'Task Scheduler'
- Create Basic Task
- The 'Create Basic Task Wizard' will appear, name the task whatever you want
- Set the Trigger to 'When the computer starts'
- Set the Action to 'Start a program'.
- You will need to browse to the program/script you wish to start (which is your .BAT batch file that starts your server).
- Depending on how your batch file works, you may need to set the "Start in (optional)" path, so the working directory of your batch file is correct. (If your batch file simply contains the "start ShooterGame ..." command, then you should set the "Start in (optional)" path of your scheduled task to the directory that contains the batch file)
- Before you create the scheduled task, click the checkbox to "open properties window" after it's created
- In the General Tab under the Security Options frame, you probably want to choose "Run whether user is logged on or not"
- I personally checked "run with highest privileges" just in case. This might not be necessary.
Linux (via systemd)[editar | editar código]
NOTE: systemd is not available for Ubuntu 14.04
As an alternative to using a script to launch the dedicated server manually, hosts running systemd can be configured to automatically start the dedicated server when the system boots. When using this method to manage the server, using
GameUserSettings.ini to specify its settings is highly recommended. Refer to Admin Game Commands for more information.
- Create a file named
/etc/systemd/system/ark-dedicated.servicewith the following contents:
[Unit] Description=ARK: Survival Evolved dedicated server Wants=network-online.target After=syslog.target network.target nss-lookup.target network-online.target [Service] ExecStartPre=/home/steam/steamcmd +login anonymous +force_install_dir /home/steam/servers/ark +app_update 376030 +quit ExecStart=/home/steam/servers/ark/ShooterGame/Binaries/Linux/ShooterGameServer TheIsland?listen?SessionName=<session_name> -server -log LimitNOFILE=100000 ExecReload=/bin/kill -s HUP $MAINPID ExecStop=/bin/kill -s INT $MAINPID User=steam Group=steam [Install] WantedBy=multi-user.target</session_name>
ExecStartline specifies the command to run in order to start the service. It uses the same syntax as the startup examples shown above (in #Server Installation), with all the same arguments, but here it's important to adjust it to reflect the location of your ARK dedicated server on the host. Use the full path to the server executable, as shown above.
Be sure to replace
<SESSION_NAME>with the desired session name for your server as well.
Finally, adjust the
Groupsettings for your host. Without these two options in
ark-dedicated.service, the dedicated server will be run as the root user. This is unsafe, as any vulnerability in the dedicated server could result in an attacker gaining remote superuser access on the host.
It's recommended to run the dedicated server in an unprivileged account used solely for this purpose. In the example above, the user account "steam" is used. It's a member of the "steam" group, which is generally created along with the account.
- To install systemd:
apt-get install systemd systemd-sysv
You will need to reboot after installation to initialize systemd.
Activate the new service so it starts automatically when the host boots by running the following command via sudo or a root shell:
# systemctl enable ark-dedicated
After running this command, the dedicated server will automatically start when the host does. The command doesn't start the server immediately, so to launch the dedicated server after enabling it, run:
# systemctl start ark-dedicated
After following these steps, your server should be up and running, and be automatically managed by the host on startup and shutdown.
Post-Setup Management[editar | editar código]
The server can be stopped by running:
# systemctl stop ark-dedicated
and its current status can be viewed (whether it's running or not) by running:
# systemctl status ark-dedicated
Note: If you need to update the
ark-dedicated.service file (to change the dedicated server's startup options or to adjust its path), run the following command to ensure your changes are applied:
# systemctl daemon-reload
Updating[editar | editar código]
To update the server when a new version is released, repeat the same SteamCMD commands shown in the previous section. Be sure to use the correct set of commands for your platform. Refer to SteamCMD's documentation for details on automating this process.
If you use the systemd startup file you can easily integrate the update-mechanism to be run before every start of the game.
SteamCMD provides additional tools to make installation and updates easier and more seamless.
Console Commands[editar | editar código]
While running the game, the command console can be accessed with either the
[~] (tilde) or
[TAB] keys (depending on game version, default configuration and your keyboard layout). Once in the console, to activate administrator commands, enter:
<admin_password> with the server's administrator password.
Refer to Admin Game Commands for a list of available commands.
If the console can't be opened in-game, exit the game, open the game's
DefaultInput.ini file (located in your Steam library in the folder named
steamapps\common\ARK\ShooterGame\Config) with a text editor and locate the line (near the bottom of the file) that reads:
Remove the semicolon (;), changing the line to read:
Save the file and launch the game. The console should be accessible.
Backing Up Server Data[editar | editar código]
To make a backup of the server data, simply copy the folder named
ShooterGame/Saved (and his content) to the desired backup location. This folder contains all tribe, player and world data for the server.
Performing a backup is recommended before updating a server to a new release.
Troubleshooting[editar | editar código]
Server Loses Characters or World Data Upon Restart[editar | editar código]
If your server isn't retaining characters or world data when it's restarted, it may not have full access to the folder where it's installed.
The first time the server is run, it should create a folder named
ShooterGame/Saved containing various configuration and save files. If the server has run at least once but hasn't created this folder, it may not have been able to create new folders and files there. Verify that the folder where the server is installed is readable and writable by the user account that actually runs the server. (For Windows servers, check the status of User Account Control)
The server software, by default, is set-up to automatically save world data every 15 minutes. If your server crashes before the first 15 minutes are up, you will not have any data saved.
Linux Server Exhibits High CPU Usage and Low Memory Usage (Below 1GB)[editar | editar código]
This can occur when the server can't open all the files it needs due to an insufficient open files limit on the host. Refer to the Linux section above and follow the procedure to increase the host's open files limit.
Tool - ARK Server Organizer[editar | editar código]
You can also use this tool to manage your server when it is installed: http://steamcommunity.com/sharedfiles/filedetails/?id=951274291
This freeware give an interface for your ARK Dedicated Server. It works with SteamCMD.
- AutoUpdate: You can choose to update and restart the server everyday to keep your server up to date. You just have to check the checkbox and to choose the update time.
- Hide Server Window: Allow you to hide the black screen of the server (Screenshot n°4). You can also close the app, it will send it in notification area and the server will still run. This function need to be set before launching the server.
- Get Public Server Address IP: You can now have the full address quicly and easily to share it with friends for example.
- NotifyIcon Settings: Allow you to Turn ON or Turn OFF Server from NotifyIcon without any visual form. You can also have access to 'Get IP Address' function.
- Portable Application: Quick start, low size, no installation required.
Notes[editar | editar código]
References[editar | editar código]
External Links[editar | editar código]
- This material is partially based on a Guide posted on the Steam Community forums by ShuwA.