Hi Josh, I did not get pound to work with websockets. I switched to ldirectord. I did this setup a year ago so I don't know if the fix in January resolved the problem. I have not tested it. I'm also using apache-websockets and have not yet switched to websocketd. Not sure if that make a difference with pound or not.
Martha Driscoll, Systems Manager North of Boston Library Exchange www.noblenet.org On Tue, Sep 3, 2019 at 9:29 AM Josh Stompro <[email protected]> wrote: > Martha, I just saw your post. We are also using pound proxy, and looking > to upgrade to 3.3 and use the web staff client. Did you get it to work > with pound. > > It looks like historically pound proxy has had trouble with websockets > [1], but there was a release early this year with a fix perhaps [2]? > > What is everyone switching to from pound? HAproxy? > > Josh > > 1 - > https://superuser.com/questions/542204/pound-configure-to-handle-websocket > 2. - > http://www.apsis.ch/pound/pound_list/archive/2019/2019-01/1547402746000#1547402746000 > > On Mon, Aug 6, 2018 at 8:41 AM Martha Driscoll <[email protected]> > wrote: > >> We are running release 3.0.9 and I can connect to the web client if I >> browse directly to one of my application servers. When I try to login via >> the load balancer I get the login screen but when I try to login it just >> refreshes the login screen. >> >> Is there something that needs to be configured for the web client to work >> through a load balancer? We are using the pound load balancer and I have >> backends setup for port 443. >> >> Martha Driscoll, Systems Manager >> North of Boston Library Exchange >> www.noblenet.org >> >> >> > > -- > Josh Stompro - IT Director > Lake Agassiz Regional Library > Desk: 218-233-3757 Ext 139 > Cell: 218-790-2110 >
