Hello team! I'm not sure if this is the proper cha...
# fleet
s
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)
l
Hi @Saulo Guilhermino. Let me check exactly what API does goquery use for running the live queries.
Looks like
fleetctl goquery
uses the following endpoint:
/api/latest/fleet/results/websocket
. Probably not working for you because of
v1
vs
latest
.
s
Oh, okay! Let me test it, just a sec
Great, it is working now! Thanks @Lucas Rodriguez!
Will all the 'v1' routes be replaced by 'latest'?
l
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.
s
Alright, thank you! 😄
l
👍