• j

    jby

    9 months ago
    Why does it try to connect to
    localhost
    ?
  • c

    Chad

    9 months ago
    Did you build the client with the allow insecure flag?
  • j

    jby

    9 months ago
    I built it with the recommended flags:
    go run ./cmd/package --type=pkg --fleet-url=localhost:8412 --insecure --enroll-secret=YOUR_FLEET_ENROLL_SECRET_HERE
    but replaced the url with the server hostname and the secret with the secret from the server
  • c

    Chad

    9 months ago
    So the insecure flag causes the client to create a local proxy to route traffic to the fleet server. Thats probably why you are seeing it try to connect to localhost
  • j

    jby

    9 months ago
    Ok, but it somehow times out
  • I’ve now tried this on a Fedora 34 client, on a Ubuntu 20.04 client and on a macOS 12.1 client and none of them show up in my fleet preview server
  • c

    Chad

    9 months ago
    Yeah you can see in the logs there is a connection issue. Could be a firewall or some other issue. Can you see when your run the client if a service is listening on port 40673 and whether its accessible?
  • j

    jby

    9 months ago
    It’s set up
  • And listening
  • I’ve had the firewalls opened up on port 8412
  • I can access the webgui
  • c

    Chad

    9 months ago
    Whats setup an listening the fleet server or the local proxy?
  • j

    jby

    9 months ago
    The local proxy
  • c

    Chad

    9 months ago
    Ok cool. Then the second thing is:
    "dial for validate: dial tcp 10.40.47.18:8412: connect: connection timed out"
    Can the host access the fleet server?
  • j

    jby

    9 months ago
    Yes
  • Ok, there was an additional FW - that I didn’t know about. My network team just informed me - and helped me - now I have connection
  • Is go a run-time requirement as well as a build-time requirement?
  • Benjamin Edwards

    Benjamin Edwards

    9 months ago
    Build time. Fleet and orbit all run as native binaries for the target OS