When setting up the Beacon its possible to route it through a reverse proxy, in the image above this is explained, The agents only have network availability to the reverse proxy server (Davecorp) However the agents will instead try and target the beacon (Flexbeacon123)

To alter the agent's behaviour to instead upload to the reverse-proxy instead of directly attempting the beacon we need to access the beacon server itself and open the beaconengine.config file-

Locally on the beacon open this file in notepad.

Within this file, you will see the following, see the circled entry.

By entering information in the networkName field and saving this file with these new details it will update the agents on their next policy update.

Keep in mind that the agents will need connectivity to perform this policy update