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
On Tue, Sep 3, 2019 at 10:52 AM Jason Stephenson wrote:
> On 9/3/19 10:11 AM, Bill Erickson wrote:
>
> > After some poking around I made 2 changes
> >
> > 1. Use an IP address (e.g. 127.0.0.1) in the proxy_pass configuration
> > instead of a hostname to bypass DNS.
> > 2. Drop the keepalive
On 9/3/19 10:11 AM, Bill Erickson wrote:
> After some poking around I made 2 changes
>
> 1. Use an IP address (e.g. 127.0.0.1) in the proxy_pass configuration
> instead of a hostname to bypass DNS.
> 2. Drop the keepalive timeout from the default of 65s to 5s or so.
There is no keepalive
Josh,
It's interesting to me that you reply to Martha's email today.
We recently started using nginx proxy on the brick heads with ldirectord
running on our load balancers. We've had issues where ldirectord dies
about one per week on each load balancer. It appears that the load
balancer is
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]?
