Skip to main content

Self-hosted machine

When using a dedicated server connected to a home / office network, there are a couple extra things you may need to configure.

Installation instructions>

Check requirements

Make sure your setup meets the hardware requirements and your machine runs a supported Operating Systems (OS).

Update machine & drivers

Make sure the machine is up-to-date after installing the OS. Outdated drivers can cause degraded performance and breaking issues.


DediConnect uses containerization software (Docker) to isolate containers, thereby reducing the potential impact of viruses and hacking threats.

In order to avoid performance penalties as much as possible is it recommended that you install DediConnect on a bare-metal machine directly. You can use software like KVM and Proxmox, but do note that this will have a slight performance impact on the hosted game servers.

Installing DediConnect inside a Hyper-V or Docker container may cause breaking issues. We do not recommend this setup as it's causing nested containerization.

Dedicated IP

In order for people and GSA to connect with your machine, you need to make sure that your internet connection has a dedicated IP (or a dynamic IP that never changes). Contact your Internet Service Provider for more information.

Port forwards

Make sure you forward all ports that GSA may use on your machine.

Those ports should be forwarded to the internal IP of your machine. Forwarding is usually done on your router. For instructions about how to forward ports on your router, please use a search engine.

forward all ports

Missing any ports may cause problems. Make sure to forward TCP & UDP for all ports.

Multiple machines on single IP

Learn what you can do when you only have a single IP (usually a home network) to host all your machines from.

Advanced stuff

We do not recommend following the steps below unless an expert on our discord advised you to do so.

How does it work?

Each machine will install using a different port offset. It's basically raising all the port numbers that GSA might use with the configured offset.


Here are some offset examples for different configurations:

2 machines:

  • Machine A -> use offset 0
  • Machine B -> use offset 1000

3 machines:

  • Machine A -> use offset 0
  • Machine B -> use offset 1000
  • Machine C -> use offset 2000


1. Install GSA script

If you haven't already, ensure you installed the GSA script on your Windows machine.

2. Open sshd_config in Notepad

Navigate to C:\ProgramData\sshand open sshd_config with Notepad.

Locate sshd_config

3. Change port

Change Port to the offset number you want to use (see example here).

Change port

4. Restart SSH

Open PowerShell and run Restart-Service sshd -Force to restart SSH.

Restart SSH via Powershell

5. Update firewall rule

Open Windows Defender Firewall and click Advanced settings.

Go to Advanced Settings in Windows Defender firewall

Then click on Inbound Rules and locate the OpenSSH Server (sshd) firewall rule. Right click the OpenSSH Server (sshd) and click on Properties in the dropdown menu.

Find right firewall rule

Finally click on Protocols and Ports and change Local port to the offset number you want to use (see example here).

Change port number

Hit OK to save the port.


Make sure to use this link to enable the hidden offset field: connect Dediconnect with special offset number >