Completely broken for me, fleet-v4.15.0
# fleet
m
Completely broken for me, fleet-v4.15.0
k
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
n
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.
Linking to the bug report issue here: https://github.com/fleetdm/fleet/issues/5993
🙌 1
m
yep that’s my bug report feel free to ask me if yas need more info
z
@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.
m
@zwass Done
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?
k
@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 ?
k
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.
k
I was able to get websockets working by updating my proxy config 😃
m
Yea I’m using nginx what are you using?
So does this mean that these websockets were not used until v4.14?
k
I think Zach mentioned in Github that they are using SockJS to emulate websockets using JS
I'm using Apache
z
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.
m
Ah well, fixed with a minor nginx configuration rejig. Glad we sorted it.
🍻 1