Why would you want to do this?
1.) Redundancy. If the main panel stops working, your other panels will continue to work if able to communicate with the database.
2.) Speed. If you have remote nodes in geographically diverse locations, having a web panel in each diverse location will give users in that region a more responsive panel as panel communication with the remote nodes in that region will have less latency.
- Must be utilizing a MySQL/MariaDB database backend. This is a general requirement for remote monitors also.
- Each panel must have its own server definition (sdef) ID. Your first/initial panel will always be ID #1 (sdef #1).
- A remote panel can share a sdef ID and license with a remote monitor, but must be ran on the same box as the remote monitor.
- Remote mode musts be enabled for the monitor on sdef ID #1. This is to allow the remote panels and auto installs from remote panels to operate properly.
- If installing a remote panel with an existing or new remote monitor; the monitor and panel should run as the same user on Linux.
- Ensure remote mode is enabled for sdef ID #1's monitor, and that the sdef id #1's panel can communication with it. More information on enabling remote mode is available here.
- Either create a new server definition within the panel, or use an already existing server definition. Take note of the ID number for this sdef.
- In the remote panel's Web.config, enter the aforementioned sdef ID in the panelsdefid key setting. If the setting does not exist you may add it
Code: Select all
<add key="panelsdefid" value="<id goes here>"/>
- Any auto-installer configs that don't use SteamCMD to update their cache; will copy the cache from sdef ID #1 if an install is initiated from a remote panel
- Auto installer configs will be copied from sdef ID #1 if an install is initiated from a remote panel
- Auto installer configs that use SteamCMD, will simply run SteamCMD to update the cache on the target remote
- If you experience frequent timeouts to remote monitors from a remote panel, you may need to allow the remote panel extra time to allow an initial connection before considering it to be unreachable. The timeout values for each sdef are in consideration of sdef ID #1's panel to each remote monitor. You may set the following setting in the remote panel's Web.config (add the config line if it's missing) to add additional time to allow for connections to be established for remote panels. The value is in milliseconds and a good starting point would be 250-500 milliseconds. This value will be added to the timeout value already set for each remote monitor. Setting this value too high will not cause any issues as long as the remote monitor is operating correctly, but when it is unreachable it may cause extremely long delays when trying to communicate to an unreachable remote monitor.
Code: Select all
<add key="remotetimeout" value="0"/>