Artem
12/08/2020, 1:47 PMzwass
12/08/2020, 4:20 PMfleetctl
? We sometimes see the browser UI having trouble rendering large result sets (though this doesn't sound like a particularly large result set). Looking at your error message though it does seem likely to be a websocket issue -- possibly a misconfiguration of nginx. Are you able to look in the network tab of the dev tools and see whether there is a successful websocket connection?kolide
in the URL paths that will wait until 4.0 as it's a breaking change for anyone using the API.Artem
12/08/2020, 4:36 PMzwass
12/08/2020, 4:40 PMArtem
12/08/2020, 4:58 PMzwass
12/08/2020, 4:59 PMproxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
defensivedepth
12/08/2020, 5:03 PMlocation ~ ^/kolide.agent.Api/(RequestEnrollment|RequestConfig|RequestQueries|PublishLogs|PublishResults|CheckHealth)$ {
grpc_pass grpcs://{{ MAINIP }}:8080;
grpc_set_header Host $host;
grpc_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_buffering off;
}
zwass
12/08/2020, 5:04 PMproxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
within the location /api/v1/osquery/
block, but I think the websocket proxy config needs to go into the other location /
block.defensivedepth
12/08/2020, 5:05 PMArtem
12/08/2020, 5:07 PMzwass
12/08/2020, 5:08 PMArtem
12/08/2020, 6:12 PM