Relay – [E] (SenderSsl) [0219B2C8] Could not connect to peer: Host not found
Introduction
This error (Could not connect to peer: Host not found) occurs when the address of our production environment has been incorrectly configured to a non-existent address. It is responsible for transmitting the collected data from each device through the Relay.![Relay Host not found 1 Relay - [E] (SenderSsl) [0219B2C8] Could not connect to peer: Host not found](https://docs.almaden.app/wp-content/uploads/2025/02/Relay-Host-not-found-1.jpg)
Explanation
Currently, we only have the production environments LAD1 and LAD2, which are automatically applied when the agent is downloaded using your account on SmartCenter.
Address “lad1-receiver.almaden.app” for the LAD1 production environment and “lad2-receiver.almaden.app” for the LAD2 production environment.
Note: Do not change it to another address; always keep the one displayed in SmartCenter after logging in.![]()
Tests
To verify if the address is correct, access:
Desktop Agent: “C:\Program Files (x86)\Automatos\Desktop Agent\adacontrol.exe“
Server Agent: “C:\Program Files (x86)\Automatos\Automatos Server Agent\asacontrol.exe“
Click on “Relay” and “Log file”, in the “Server” field, it will display the address it is trying to communicate with.![Relay Host not found 4 Relay - [E] (SenderSsl) [0219B2C8] Could not connect to peer: Host not found](https://docs.almaden.app/wp-content/uploads/2025/02/Relay-Host-not-found-4.jpg)
Fix
Desktop Agent: “C:\Program Files (x86)\Automatos\Desktop Agent\adacontrol.exe“
Server Agent: “C:\Program Files (x86)\Automatos\Automatos Server Agent\asacontrol.exe“
Click on “Configuration > Relay > Protocols” and correct the address in the “Name or IP” field.
By default, communication is SSL (Secure Socket Layer), and the port is 443.![Relay Host not found 3 Relay - [E] (SenderSsl) [0219B2C8] Could not connect to peer: Host not found](https://docs.almaden.app/wp-content/uploads/2025/02/Relay-Host-not-found-3.jpg)
If you still need support after following all the instructions, collect the logs and open a case at https://support.almaden.ai/ with evidence of the reported issue.
