Jaideep Natu10/01/2021, 6:18 AM
# fleetctl setup --email <email> --name <name> --org-name <org> --debug RoundTrip error: dial tcp 127.0.0.1:8412: connect: connection refusederror setting up Fleet: POST /api/v1/setup: do request: Post "<https://127.0.0.1:8412/api/v1/setup>": dial tcp 127.0.0.1:8412: connect: connection refused
Sarah Gillespie10/01/2021, 5:41 PM
Jaideep Natu10/01/2021, 6:10 PM
zwass10/04/2021, 5:17 PM
usually means that there is no server listening on that port. One easy way to double-check is to try
curl -k -v <https://127.0.0.1:8412>
. I think you're going to get
fleetctl debug connection <https://127.0.0.1:8412>
with any of these methods.
Jaideep Natu10/04/2021, 9:38 PM
Debugging connection to 127.0.0.1; Configuration context: none - using provided address; Root CA: (system); TLS: secure. Success: can resolve host 127.0.0.1. Success: can dial server at 127.0.0.1:8412. Fail: agent API endpoint: request failed: Post "<https://127.0.0.1:8412/api/v1/osquery/enroll>": x509: cannot validate certificate for 127.0.0.1 because it doesn't contain any IP SANs
zwass10/05/2021, 12:29 AM
and then the
fleetctl config set --tls-skip-verify=true
Jaideep Natu10/05/2021, 4:22 PM
I don't recall fleetctl not executing without an error.
404 page not found Fleet has already been setup
zwass10/05/2021, 4:25 PM
Jaideep Natu10/05/2021, 5:06 PM
Login failed: login received status 401 Authentication failed: Authentication failed
zwass10/05/2021, 9:52 PM
Jaideep Natu10/05/2021, 10:02 PM
zwass10/05/2021, 10:34 PM
those are the default credentials that preview sets up.
Jaideep Natu10/05/2021, 10:47 PM
zwass10/05/2021, 10:49 PM
automatically creates that user, so Fleet is already set up. If you want to create another user you'll need to use
or the UI.
fleetctl user create