Replies: 1 comment 2 replies
-
I have the same issue. I found a workaround. I added my firewall's IP address in the elasticfleet / config /server / custom_fqdn field. Then I copied this file from default to local and modified line 167 it so it would use IP instead of DNS for the fqdn. Then ran a highstate to apply the changes. It's not elegant, but it works.
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have Security Onion sitting behind a PFSense firewall. The certificates that are generated by the so-elastic-agent-get-installers do not have the ability to have a Subject Alternative Name (SAN). This would allow the agent to verify the certificate correctly when connecting to the firewall's hostname or IP. If the SAN could get pulled from the elasticfleet / config /server / custom_fqdn field, I think that would solve the issue.
I am using SO 2.4.50 with the downloaded elastic-agent files from SO manager.
Beta Was this translation helpful? Give feedback.
All reactions