https://github.com/osquery/osquery logo
Join Slack
Powered by
We've built the Fleet package with fleetctl, inclu...
# fleet
p
We've built the Fleet package with fleetctl, including our server certificate. Yet during deployment we still can't seem to be able to enroll our endpoints (all macOS laptops):
Copy code
W0626 14:49:27.032124 -139899904 tls_enroll.cpp:101] Failed enrollment request to <https://fleetdm.XXXXX/api/v1/osquery/enroll> (Request error: certificate verify failed) retrying...
What are we doing wrong there?
l
Hi @Pierre N! • Does 
curl <https://fleetdm.XXXXX/api/v1/osquery/enroll>
work? • How was the package generated? (
fleetctl package ...
)
p
Hi @Lucas Rodriguez sorry for taking so long, we made some progress and we are pretty sure it's linked to our security controls. 
curl enroll
doesn't work, but it also doesn't work on properly running endpoints and if we hardcode the IP it works fine on new endpoints.
We tried both normal package generation from the portal and the generation with the server cert, both lead to the same error which seems related to the fleetdm.XXXXX resolution
l
Hi @Pierre N! 
curl enroll
doesn't work, but it also doesn't work on properly running endpoints and if we hardcode the IP it works fine on new endpoints.
Sorry, by work I meant that SSL/TLS works but then you get a 403 or something. If you are getting certificate verification issues with curl then it means something's off with the server's certificate.
p
Yes looking into this at the moment
36 Views
Open in Slack
PreviousNext
Powered by