...
| Option | Description |
|---|---|
| Enable | Toggles Remote Management access on and off |
| API Key | Security key required by MultiSite to access Site Manager remotely. If this key is changed, MultiSite access will fail until MultiSite is updated with the new key |
| Copy | Copies the API key to the clipboard |
| Generate New Key | Generates a new random key. The key is not in effect until Save is pressed |
Port Redirection
Finally, the interface port of Site Manager must be accessible to the internet for incoming connections so that MultiSite can connect to it. This can be on any port of an internet accessible IP address or domain name.
For example, if Site Manager is running on an internal host called sm-server running on the default port of 2904, your internal network can be configured to route incoming connections on sm.yourdomain.com on port 44853 to the internal server sm-server port 2904. MultiSite can then be configured to manage this Site Manager using the externally configured address, port and the API key.
| Info |
|---|
| Info |
All communications between MultiSite and Site Manager use RSA 2048 encryption, no unencrypted data is transferred |
Communications Ports and IP Addresses
The MultiSite connection is based on outgoing traffic from the Site Manager installation.
| Server | Protocol | Port | IP Addresses | Purpose |
|---|---|---|---|---|
| tunnel.msadmin.macrium.com | HTTPS | 443 | 40.84.156.200 13.84.162.176 13.65.241.157 | To establish an initial connection to MultiSite, Site Manager makes an outgoing HTTPS connection to the Macrium servers. |
| tunnel.msadmin.macrium.com | SSH | 1004 | 40.84.156.200 13.84.162.176 13.65.241.157 | Site Manager uses an outgoing SSH connection to transfer information to MultiSite. Please note that the port used may change in future releases |
The IP addresses provided may be changed or added to in future releases. We recommend adding any necessary firewall rules by DNS name if possible.