- In the web panel, go to the Settings Page-->Server Definitions.
- You should now be at the server definitions page. Scroll to the bottom of the page and enter a name for the new definition and click add.
- Fill in the information for your server. Be sure to enter the address, port (default is tcp/3432), and password correctly. TIP: For the address setting in the panel, use an IP address if possible. If your server has any DNS issues, the panel will not be able to talk to the remote node or operations could talke a long time while resolving.
- Click the Update button. When the page refreshes, select the new definition from the drop down list at the top of the page.
- Keep a note of the ID number assigned to this definition. This number should be greater than 1, if it isn't, you did something wrong.
- Install and license the monitor (see license section below for guidance) on the remote host if it hasn't been already. Installer for the monitor is available in the manual install package.
- Edit the config file (Windows\system32\ugccmon.cfg on Win; ugccmon.cfg in same folder as binary on Linux) for the monitor, be sure the [Remote], [Port], [Secret] settings are set as they were configured for the definition in the panel. The ID number you took note of earlier is used for the [ID] setting in the monitor's configuration file.
- Enter the details for your database. Use the same database the panel uses. More notes on database below.
- Once the monitor is licensed, you should be able to start it.
- You can then test the configuration by using the test button in the server definition page of the panel for that node.
The monitor will create its own .licrm license request file in the path configured in ugccmon.cfg for the log file location. The file will be named <hostname>.licrm.
Game Server Setup
When setting up a new game server in the panel, on the general tab there is a 'Server Location' setting, this contains all the server definitions defined so far. Choose the remote node that contains the game server, and the panel will send its commands to the remote monitor on that node. The remote monitor will then start/stop/etc that server.
Notes About Databases and Remote Monitors
In general if the web based control panel will be managing a remote monitor setup on a different server, you will need to use MySQL. Also make sure your MySQL server allows connections from the IPs of your remote monitors.
SQLite and Remote Monitors
The only time it's suggested to use sqlite with a remote monitor is when you're using linux and the monitor is running on the same host as the web panel. This allows the monitor to manage all tasks (i.e. starting and stopping servers). Typically the panel and monitor run as different users on Linux; and setting up the monitor in remote mode fixes this issue with managing permissions for both.