On Fri, Feb 2, 2018 at 3:42 AM, StephenDart <stephen.d...@gmail.com> wrote:
> Will post the config when i am back home, but actually there is only one > backend so sticky sessions arent a problem, there is only one possible in > the config to go to. > Any traffic for /guacamole will go to a single server. > > I think there must be something regarding how haproxy maybe waits for a > session to complete, I had hoped that the http-server-close may have helped > but it doesnt appear to. > This really shouldn't impact the API at all - at least, you shouldn't see any 404 errors or anything like that. I'm not sure about the actual connection stream, though. Two things come to mind: - Some sort of incompatibility in how HAProxy handles WebSocket traffic, particularly if it is trying to establish it and then dropping it. I'm not sure off the top of my head if HAProxy supports, doesn't support, or is ignorant of the use of WebSocket. - A parameter is being dropped from one of the API or tunnel calls, like the token, somewhere along the way - perhaps in HAProxy somewhere. -Nick
