I was testing this yesterday and thought I was losing my mind !
Yes I can also confirm that queries on 4.15 did not return results, continued loading on screen. Do return results on 4.13.2
06/01/2022, 2:28 PM
Hey, sorry you’re experiencing this issue. The Fleet team is looking into this.We’ll follow up with a bug report issue on GitHub so that you can track the progress of the investigation.Thank you for the helpful error messages.
yep that’s my bug report feel free to ask me if yas need more info
06/03/2022, 12:07 AM
@Keith Swagler@Mystery Incorporated and anyone else experiencing this... Can you please help us out with more details as requested in https://github.com/fleetdm/fleet/issues/6049? A number of folks have tried to reproduce this internally and we have not been able to.
06/03/2022, 11:11 AM
Looking at the error looks like there is a SocksJS mismatch between 1.6.0 and then 1.6.1 is being used in an iframe?
06/03/2022, 12:33 PM
@zwass can do
After bypassing the Web proxy I have Queries are working again.@Mystery Incorporated do you have a proxy/WAF in front of your instance ?
06/03/2022, 4:40 PM
Thanks for the update @Keith Swagler. If anyone else is experiencing this issue, please check that you don't have a proxy blocking those connections and let us know what you see.
06/03/2022, 5:36 PM
I was able to get websockets working by updating my proxy config 😃
So does this mean that these websockets were not used until v4.14?
06/06/2022, 3:21 PM
I think Zach mentioned in Github that they are using SockJS to emulate websockets using JS
I'm using Apache
06/06/2022, 3:35 PM
Websockets have been used since the earliest versions of Fleet, with sockjs as a fallback. Sockjs has been very unreliable that entire time, but I'm not sure what could have changed recently that would have made it stop working entirely.
06/14/2022, 3:38 PM
Ah well, fixed with a minor nginx configuration rejig. Glad we sorted it.