General Server Setup Information

{{CatUp|Dedicated Server Setup}}


= Information in this section applies to all Operating Systems =

== Publishing a server ==

Once you have your server running, if it is your own machine, you have to let people connect to it. To do that, you have to open a pinhole in your firewall. This is not the place to go into the reasons why you should have a separate hardware firewall; we will simply assume that you do. Making a pinhole will require that you log in to your firewall (usually from Internet Explore, Firefox, or some other browser), lock your server to a single private IP address, and then direct a port to that address.

=== Locking a machine to a private IP address ===

The server must always be at the same address on your in-house network, otherwise game requests will go somewhere else and nobody will be able to log in. So you must ensure that every time your machine is turned on or connected, it gets the same address. The technique used to assign addresses to machines is called DHCP. On most hardware firewalls, on the DHCP page you have options to set "reservations". Many are particularly friendly in that you can find your machine's DHCP "lease" and just copy that into a reservation. Otherwise, you have to enter the "MAC address" of the server, and the IP address, into the reservation manually.

Once you have set a reservation for your server, record the IP address.

=== Port redirection ===

For the server to be reachable, network requests must reach it. On most hardware firewalls, you need to set this in the Advanced pages. You are looking for "pinholes", "virtual servers", or "port redirects". Once you have found the page you need, you want to set a rule that says incoming UDP requests on port 27015 are sent to port 27015 on the IP address of your server. 

NOTE that if you set a non-standard port when you started the server, as described above, then the port you want to set to be redirected is the same as the nonstandard port. So for instance, if you are running a TF2 server on one machine at IP address 192.168.0.105 and a GM server on another machine at address 192.168.0.101, you would set the TF2 server to the default port 27015 and the GM server to port 27035, as described above. You would then set two port redirect rules, one that directs UDP port 27015 traffic to port 27015 at 192.168.0.105, and one that redirects UDP port 27035 traffic to port 27035 at 192.168.0.101.

Experience indicates that it is not a good idea to have two servers using the same UDP port and trying to use the port remap in the firewall to  expose different external port numbers. The port number of the server itself apparently needs to be identical to the port number visible to the Internet at large.

Once you've completed this step, you may want to start your server and visit [http://cpfx.ca/srcds/portcheck.php this SRCDS port checking utility] to verify that the forwarding is working and that people will be able to connect to your server.

=== Done ===

Once your firewall is accepting traffic and forwarding it to your server, you are done. When your server starts up, it contacts the Steam servers, and from then on it will show up in the available server lists for GM, as long as it stays alive.

= Fastdownload (sv_downloadurl) =

{{:Setting_up_sv_downloadurl}}

= SetupArrayProps_R: array prop '(null)' is at index zero. =

If you receive this message trying to run your Garry's Mod dedicated server, it means it is conflicting with the Team Fortress 2 version of the source engine. You can fix this by first updating all your other games, and then running update on Garry's Mod by using the following command (notice the -verify_all -retry):

 hldsupdatetool -command update -dir <yourdirectory> -game "garrysmod" -verify_all -retry

Thanks to g0dFather at facepunch.com (link: http://www.facepunch.com/showpost.php?p=16926473&postcount=21)

A second way of fixing this error is to delete everything in orangebox/bin and orangebox/garrysmod/bin and then updating Garry's Mod through the hldsupdatetool.

= tier0.dll error =
''The procedure entry point GetThreadedLoadLibraryFunc could not be located in the dynamic link library tier0.dll''

Go to the root directory of your dedicated server (C:\srcds if you followed this tutorial exactly) , and rename tier0.dll and vstdlib.dll to something else. Now try starting your server again.


= How many slots can I get on my connection? =
In my experience, each player slot takes up about 32 kilobits per second. That's upload speed. As long as your download speed isn't the bottleneck, the following seems to hold:

* 64kb/s = 2 players max
* 128kb/s = 4 players max
* 256kb/s = 8 players max
* 512kb/s = 16 players max
* 1Mb/s = 32 players max
* 2Mb/s = 64 players max

Those are calculated values. They may be not correct on every PC/Server, due many factors would need to be calculated in.

= Extra content =
If you don't wish to add extra content (Counter-Strike: Source, Day of Defeat: Source), then you can skip this section.

==Counter Strike: Source==
The following lines will add Counter Strike:Source content to your server

===Windows / ReactOS:===
 hldsupdatetool -command update -game "Counter-Strike Source" -dir .
===Linux:===
{{Info | text = If css does not mount, open up the css folder (root/css) and move the cstrike folder in it to the orangebox folder (root/orangebox). | }}
 ./steam -command update -game "Counter-Strike Source" -dir .
===Wine:===
 wine hldsupdatetool -command update -game "Counter-Strike Source" -dir .

==Day of Defeat: Source==
The following lines will add Day of Defeat:Source content to your server

===Windows / ReactOS:===
 hldsupdatetool -command update -game "dods" -dir .
===Linux:===
 ./steam -command update -game "dods" -dir .
===Wine:===
 wine hldsupdatetool -command update -game "dods" -dir .

==Half Life 2: Deathmatch==
The following lines will add Half Life 2: Deathmatch content to your server

===Windows / ReactOS:===
 hldsupdatetool -command update -game "hl2mp" -dir .
===Linux:===
 ./steam -command update -game "hl2mp" -dir .
===Wine:===
 wine hldsupdatetool -command update -game "hl2mp" -dir .

==Team Fortress 2==
The following lines will add Team Fortress 2 content to your server

===Windows / ReactOS:===
 hldsupdatetool -command update -game "tf" -dir .
===Linux:===
 ./steam -command update -game "tf" -dir .
===Wine:===
 wine hldsupdatetool -command update -game "tf" -dir .

==Episodic content==
The following lines will add the episodic content to your server (episode 1 and 2)

===Windows / ReactOS:===
 hldsupdatetool -command update -game "episode1" -dir .
===Linux:===
 ./steam -command update -game "episode1" -dir .
===Wine:===
 wine hldsupdatetool -command update -game "episode1" -dir .

==Left 4 Dead/Left 4 Dead 2 content==
The following lines will add content from Left 4 Dead to your server.
To install content for Left 4 Dead 2, replace "left4dead" with "left4dead2".

===Windows / ReactOS:===
 hldsupdatetool -command update -game "left4dead" -dir .
===Linux:===
 ./steam -command update -game "left4dead" -dir .
===Wine:===
 wine hldsupdatetool -command update -game "left4dead" -dir .

== Portal ==
Portal is single-player game, and thus, you will need to extract the content from the GCFs manually. All of these go into the <b>orangebox/</b> subfolder of your srcds folder:

 portal content.gcf
 portal english.gcf