Saulo Guilhermino
07/04/2022, 7:47 PMgoquery
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
07/04/2022, 8:15 PMfleetctl goquery
uses the following endpoint: /api/latest/fleet/results/websocket
. Probably not working for you because of v1
vs latest
.Saulo Guilhermino
07/04/2022, 8:20 PMLucas Rodriguez
07/04/2022, 8:27 PMv1
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
07/04/2022, 8:28 PMLucas Rodriguez
07/04/2022, 8:28 PM