Jaideep Natu
10/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 Gillespie
10/01/2021, 5:41 PMJaideep Natu
10/01/2021, 6:10 PMzwass
10/04/2021, 5:17 PMlocalhost
? connection refused
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>
.fleetctl debug connection <https://127.0.0.1:8412>
. I think you're going to get connection refused
with any of these methods.Jaideep Natu
10/04/2021, 9:38 PMDebugging 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
zwass
10/05/2021, 12:29 AMfleetctl config set --tls-skip-verify=true
and then the fleetctl setup
command again.Jaideep Natu
10/05/2021, 4:22 PM404 page not found
Fleet has already been setup
I don't recall fleetctl not executing without an error.zwass
10/05/2021, 4:25 PMJaideep Natu
10/05/2021, 5:06 PMLogin failed: login received status 401 Authentication failed: Authentication failed
zwass
10/05/2021, 9:52 PMfleetctl preview
?Jaideep Natu
10/05/2021, 10:02 PMzwass
10/05/2021, 10:34 PM<mailto:admin@example.com|admin@example.com>
admin123#
those are the default credentials that preview sets up.Jaideep Natu
10/05/2021, 10:47 PMzwass
10/05/2021, 10:49 PMfleetctl preview
automatically creates that user, so Fleet is already set up. If you want to create another user you'll need to use fleetctl user create
or the UI.