Logpoint Collector cannot connect to a Distributed Logpoint behind a NAT (public network)
Reference: LP-73341
Date Published: 2026-03-10
Affected Product: Logpoint
Affected Version: v7.8.0
Fix Version: v7.10.0
Description:
|
Logpoint Collector (LPC) fails to connect to a Distributed Logpoint deployed behind NAT (a public network). Logpoint enforced strict HTTPS certificate validation to help prevent man-in-the-middle (MITM) attacks and ensure secure communication between the Distributed Logpoint and LPC. This means the LPC only trusts the connection if the certificate presented by the Distributed Logpoint matches the address (IP/DNS) used to connect. When the public IP is missing from the certificate, the LPC/Search Head rejects the certificate, and the connection fails. |
Workaround:
If your deployment requires a public IP for connectivity, add the public IP address of the Distributed Logpoint as a Server Alias so it’s included in the certificate, and the LPC is connected.
- In the Distributed Logpoint UI, go to Settings >> System Settings and click System Settings.
- Select General.
- In Server Alias, enter or update the public IP address used to reach the Data node.
- Click Save Changes.
Support
If you have any questions or require assistance, create a support ticket.
Comments
Article is closed for comments.