Why does it try to connect to `localhost` ?
# fleetj
jby
11/04/2021, 9:00 AMWhy does it try to connect to
localhostc
Chad
11/04/2021, 9:01 AMDid you build the client with the allow insecure flag?
j
jby
11/04/2021, 9:03 AMI built it with the recommended flags:
go run ./cmd/package --type=pkg --fleet-url=localhost:8412 --insecure --enroll-secret=YOUR_FLEET_ENROLL_SECRET_HEREc
Chad
11/04/2021, 9:04 AMSo 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
11/04/2021, 9:04 AMOk, but it somehow times out
jby
11/04/2021, 9:06 AMI’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
11/04/2021, 9:11 AMYeah 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
11/04/2021, 9:12 AMIt’s set up
jby
11/04/2021, 9:12 AMAnd listening
jby
11/04/2021, 9:14 AMI’ve had the firewalls opened up on port 8412
jby
11/04/2021, 9:14 AMI can access the webgui
c
Chad
11/04/2021, 9:16 AMWhats setup an listening the fleet server or the local proxy?
j
jby
11/04/2021, 9:18 AMThe local proxy
c
Chad
11/04/2021, 9:19 AMOk cool. Then the second thing is:
"dial for validate: dial tcp 10.40.47.18:8412: connect: connection timed out"j
jby
11/04/2021, 9:19 AMYes
jby
11/04/2021, 9:24 AMOk, there was an additional FW - that I didn’t know about. My network team just informed me - and helped me - now I have connection
👍 1
jby
11/04/2021, 9:29 AMIs go a run-time requirement as well as a build-time requirement?
b
Benjamin Edwards
11/04/2021, 1:46 PMBuild time. Fleet and orbit all run as native binaries for the target OS
5 Views