The LinuxGSM Dashboard has been released in version 2.1.0.

The LinuxGSM Dashboard is a web interface for managing dedicated game servers run on Linux with the LinuxGSM command line tool.

After the bug fix update version 2.0.1, the new release brings an optional proxy for game traffic: players connect to a rented server with a public IP, your machine at home opens no port, and the game server still sees the real IP of the players. Traffic runs through an encrypted WireGuard tunnel. It also adds a new logo and favicon, plus fixes for Source servers in host mode and copy buttons over HTTP.

This release adds an optional proxy for game traffic: players connect to a rented server, your machine at home opens no port, and your game servers still see the real IP of the players.

Highlights

• Game traffic proxy. Choose a machine with a public IP as the proxy under Settings > Proxy. Players connect to its address, and the traffic reaches your game server through an encrypted WireGuard tunnel. Bans and logs keep working, because the game server sees the real IP of the players. Nothing is installed or changed until you click Set up proxy, and removing the proxy takes everything back, including the packages it installed.
• Steam lists your server at the proxy. Name the Linux user of the game server under Outgoing traffic, and Steam sees the proxy’s address instead of your line. Everything of this user then goes through the proxy, including updates of many GB.
• Works next to your firewall. ufw and Docker no longer block the tunnel. The dashboard keeps its rules in place, also if ufw or Docker are added later.
• Address on the server card. A published server shows the address for players, ready to copy. Administrators can publish a server or take it off directly on the card, and LinuxGSM’s alerts and details show the proxy’s address.
• A new look. The dashboard has its own logo and favicon, and a new About tab under Settings links to the project on GitHub.

Fixes

• Source servers in host mode show players and map again.
• Copy buttons now also work over plain HTTP.

Good to know

• Both machines must be in the same dashboard, as the dashboard’s own machine or as a node with read-write access, and run in host mode. Docker mode is not supported yet.
• Both machines connect to the dashboard, so it usually runs on the machine with the public IP. A dashboard at home without a public address cannot use a rented proxy yet.
• Your provider’s firewall cannot be opened from the dashboard. Open UDP 51820 and the game ports there. firewalld also has to be opened by hand; the setup tells you how.
• “Tunnel connected” is about the tunnel. To be sure that players get through, test with a game client from outside.
• All game traffic runs through the proxy, so it should be close to your players and your game server. Its traffic volume counts twice.

Upgrade notes

• Update nodes to 2.1 as well: dashboard and nodes must run the same minor version.
• Without a proxy nothing changes.

Source: GitHub