Self-hosted Hyperion server: specifying the IP address reported to Core

By default, self-hosted Hyperion servers have their external / public-facing IP address reported to the Core management system by an external service.

There are instances where this automatically-reported IP address may not match the desired IP address that should be shown in the Core dashboard; as some examples:

• An external router/firewall has multiple public IP addresses available, but the router/firewall is reporting one public address to the Core management system, instead of a separate public IP address that was set aside for use by the Hyperion server behind that router/firewall.
• Multiple Hyperion servers are behind a firewall with multiple public IP addresses assigned to it, but all outbound traffic is reported as originating from just a single public IP address instead of the one intended for each Hyperion server.

The following steps allow you to bypass the outside IP address reporting services and instead specify the exact IP address shown in the Core Dashboard.

Step 1: Use your preferred command-line (nano, vi, etc.) or GUI-based text editor to modify the /etc/proton.toml configuration file; for example, the following command uses the vi editor with a user account that has sudo privileges:

sudo vi /etc/proton.toml

Step 2: If it's not already present, add the following two lines to the top of the proton.toml configuration file: 

## Define IP address reported to Core
Host = ""

Step 3: Insert the IP address between the double quotes on the Host = line.

This is the external, public IP address that should be reported to Core management system by the self-hosted Hyperion server.

In the below example, a reserved public IP address of 198.51.100.69 will be shown in the Core interface regardless of the actual public IP address that's used.

## Define interface name to obtain mac address and host from 
Host = "198.51.100.69"

NOTE: be sure to double check this entry! Core will route all encoders and decoders trying to connect to that server to the specified IP address, so an incorrect address will prevent encoders or decoders from reaching your server!

Step 4: Restart the Hyperion process

sudo systemctl restart sputnik.service sputnik-ui.service proton.service

The dashboard in the Core management system should update and show the new IP address being reported by the self-hosted Hyperion server.