On Fri, Aug 12, 2016 at 05:08:11PM -0400, Jeff Dyke wrote:
> On Fri, Aug 12, 2016 at 4:49 PM, Roman Arutyunyan wrote:
>
> > On Fri, Aug 12, 2016 at 04:07:26PM -0400, Jeff Dyke wrote:
> > > Thank you Roman, i knew it would be painfully obvious once the solution
> > was
> > > presented to me
>
On Fri, Aug 12, 2016 at 4:49 PM, Roman Arutyunyan wrote:
> On Fri, Aug 12, 2016 at 04:07:26PM -0400, Jeff Dyke wrote:
> > Thank you Roman, i knew it would be painfully obvious once the solution
> was
> > presented to me
> >
> > Very much appreciate it!
>
> Just to clarify - you obviously have
On Fri, Aug 12, 2016 at 04:07:26PM -0400, Jeff Dyke wrote:
> Thank you Roman, i knew it would be painfully obvious once the solution was
> presented to me
>
> Very much appreciate it!
Just to clarify - you obviously have to specify another port in the new "listen"
directive.
>
> Jeff
>
> O
Thank you Roman, i knew it would be painfully obvious once the solution was
presented to me
Very much appreciate it!
Jeff
On Fri, Aug 12, 2016 at 2:29 PM, Roman Arutyunyan wrote:
> Hello,
>
> On Fri, Aug 12, 2016 at 02:08:55PM -0400, Jeff Dyke wrote:
> > i have configured haproxy 1.6 and n
Hello,
On Fri, Aug 12, 2016 at 02:08:55PM -0400, Jeff Dyke wrote:
> i have configured haproxy 1.6 and nginx 1.10.1 and all is well, but i'd
> like to be able to access the servers directly on occasion and not through
> haproxy. Mainly this is done for troubleshooting or viewing a release
> before
i have configured haproxy 1.6 and nginx 1.10.1 and all is well, but i'd
like to be able to access the servers directly on occasion and not through
haproxy. Mainly this is done for troubleshooting or viewing a release
before it goes out to the public (its off the LB at the time).
Unfortunately acc
