Title
#fleet
Saulo Guilhermino

Saulo Guilhermino

07/04/2022, 7:47 PM
Hello team! I'm not sure if this is the proper channel, but I'm getting the following error when trying to test
goquery
within fleetctl:
.connect: ScheduleQueryAndWait call failed: upgrade live query result websocket: websocket: bad handshake
I assume this is related to our infrastructure security controls regarding websocket routes. In my deployment I have to specify which routes are websockets (currently only
/api/v1/fleet/results
). So my real question is, what routes do I need to allow for Goquery to work properly? (If the issue is about that)
Lucas Rodriguez

Lucas Rodriguez

07/04/2022, 8:15 PM
Hi @Saulo Guilhermino. Let me check exactly what API does goquery use for running the live queries.
8:19 PM
Looks like
fleetctl goquery
uses the following endpoint:
/api/latest/fleet/results/websocket
. Probably not working for you because of
v1
vs
latest
.
Saulo Guilhermino

Saulo Guilhermino

07/04/2022, 8:20 PM
Oh, okay! Let me test it, just a sec
8:23 PM
Great, it is working now! Thanks @Lucas Rodriguez!
8:23 PM
Will all the 'v1' routes be replaced by 'latest'?
Lucas Rodriguez

Lucas Rodriguez

07/04/2022, 8:27 PM
The Fleet API supports versioning. Currently
v1
and
latest
work. We will let people know in advance when we decide to drop support for
v1
. So no need to rush any changes yet.
Saulo Guilhermino

Saulo Guilhermino

07/04/2022, 8:28 PM
Alright, thank you! 😄
Lucas Rodriguez

Lucas Rodriguez

07/04/2022, 8:28 PM
👍