VM | Agent Proxy Configuration & Registration

Overview

This article details the configuration requirements for the Aembit Agent Proxy on Linux. It covers how to properly link the Agent Proxy to the Agent Controller and resolve registration failures where the Agent Proxy is active but unable to authenticate and register with the Agent Controller.

Relates To

• Deployment Type: Linux Virtual Machine

• Components: aembit-agent-proxy, aembit-agent-controller

• Configuration: /etc/systemd/system/aembit_agent_proxy.service

Cause (The Symptoms)

Follow this guide if the Proxy service is running but you observe:

• Proxy Logs: Failed to register with Agent Controller: Connection Refused.

• Symptom: The Agent Proxy is unable to register itself with the Agent Controller

• Symptom: The Agent Proxy service fails to start or remains in a "Connecting" state indefinitely.

Solution

Verify Configuration & Agent Proxy Registration

1. Validate the Agent Controller Endpoint The Agent Proxy must be pointed to the Agent Controller's listening address. On Linux, this is defined during installation or manually edited in the service unit.

• Check the Configuration: cat /etc/systemd/system/aembit_agent_proxy.service | grep AEMBIT_AGENT_CONTROLLER

• Standard Ports:

  • HTTP: http://<agent-controller-host>:5000

  • HTTPS: https://<agent-controller-host>:5443

2. Verify Local Connectivity Ensure the Agent Proxy can "reach" the Agent Controller host on the designated port. Run this from the VM where the Proxy is installed:

# For HTTP
curl -v http://<agent-controller-host>:5000/health

# For HTTPS
curl -v -k https://<agent-controller-host>:5443/health

• Success: HTTP/1.1 200 OK

• Failure: Connection refused. This indicates the Agent Controller is either down, listening on a different interface, or another environmental element is present between the services.

3. Reload and Restart Service If you make changes to the .service unit file to fix the URL or Port, you must reload the systemd daemon:

sudo systemctl daemon-reload
sudo systemctl restart aembit_agent_proxy
sudo systemctl status aembit_agent_proxy