Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

is there a way to run fleet on the standard https port (443)?

when I use server_address=0.0.0.0:443 I get a `permission error` as normal user (expected since it’s a priv port) and then `Failed to start: initializing service: initializing osquery logging: create filesystem status logger: create new raw logger: open /tmp/osquery_status: permission denied`
if I run via sudo

<@U028T596B50> yeh honestly I'd set up a reverse proxy using nginx. I'm going to do this myself, gives you a bit more control for e.g. you can split the SSL termination to present a Let's encrypt certificate for the web UI, yet still use your self signed cert for osquery daemons, etc.

Your first error is expected, however the second is very unusual -- A permission error on a file in `/tmp` when running as root? Can you share the full command and output?

<@U0JFM04MS> <https://github.com/fleetdm/fleet/blob/main/docs/2-Deploying/3-Example-deployment-scenarios.md#running-the-fleet-server-1> added sudo to that.

Can you `sudo ls -l /tmp/osquery_status` and show the results? We are looking to see if there are unusual permissions on that file.