Hi, I got the "connecting" status on Fleet Desktop...
# fleet
s
Hi, I got the "connecting" status on Fleet Desktop but not from the portal Fleet UI. It seems that endpoint is connected to Fleet already. Is it normal? How can I fix this? Thank you
r
hey, could you share your logs? • Fleet desktop logs:
~/Library/Logs/Fleet/fleet-desktop.log
fleetd
logs:
/var/log/orbit/orbit.stderr.log
s
because of the self-signed certificate?
r
@Sirisak Kangman you're right! that's the cause 👍 In that case, you’ll need to either include the full certificate bundle to osquery, or use the
—insecure
flag when generating packages using
fleetctl
(only recommended in development environments) • https://fleetdm.com/docs/deploying/faq#how-do-i-fix-certificate-verify-failed-errors-from-osquerydhttps://fleetdm.com/docs/deploying/faq#why-arent-my-osquery-agents-connecting-to-fleet
s
Ohh!! I thought just bundled the certificate with the package was enough for a self-signed. Thanks @roberto 🙂