Hello, I'm getting the error below. What am I doing wrong?

# 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

@Jaideep Natu Have you tried using port 8080 instead?

yes same result with 8080

@Jaideep Natu do you have a Fleet server running on

localhost

?

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>

.

curl was successful, got a HTTP 200 OK. fleetctl debug connection gave an error:

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

Try

fleetctl config set --tls-skip-verify=true

and then the

fleetctl setup

command again.

Strange, now I get -

404 page not found
Fleet has already been setup

I don't recall fleetctl not executing without an error.

Can you access the Fleet server via the browser now?

yes I can, thank you

Are you using

fleetctl preview

?

yes preview is running concurrently, the password issue is with fleetctl login and the web UI

Try

<mailto:admin@example.com|admin@example.com>
admin123#

those are the default credentials that preview sets up.

why didn't the username from the config file work though? do I need to restart fleet for that?

fleetctl 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.