On Sat, Oct 31, 2020 at 5:13 AM Francis Daly wrote:
> On Fri, Oct 30, 2020 at 10:45:14PM +0530, Kaushal Shriyan wrote:
> > On Fri, Oct 30, 2020 at 4:35 AM Francis Daly wrote:
>
> Hi there,
>
> > > What does the nginx access log or error log say happened to that
> request?
>
> > I am seeing this
On Fri, Oct 30, 2020 at 10:45:14PM +0530, Kaushal Shriyan wrote:
> On Fri, Oct 30, 2020 at 4:35 AM Francis Daly wrote:
Hi there,
> > What does the nginx access log or error log say happened to that request?
> I am seeing this below message when I hit
> http://219.11.134.114/test/_plugin/kibana/
Hello!
On Thu, Oct 29, 2020 at 10:23:33PM +0100, Robert Naundorf wrote:
> I have a question on TLS session resumption with client-side session
> tickets and its implementation in nginx.
>
> RFC 5077, section 3.3, paragraph 2 reads:
> If the server successfully verifies the client's ticket, then
Hello!
On Thu, Oct 29, 2020 at 01:02:57PM -0500, Jordan von Kluck wrote:
> I am hoping someone on the community list can help steer me in the right
> direction for troubleshooting the following scenario:
>
> I am running a cluster of 4 virtualized nginx open source 1.16.0 servers
> with 4 vCPU c
On Fri, Oct 30, 2020 at 11:29:39AM -0400, bobfang_sqp wrote:
> Hi I am using nginx as a load balacer and I require sticky session (same
> client always go to the same server), for this purpose I use this following
> setup:
>
>
> upstream backend {
>ip_hash;
>server host1:8000;
On Fri, Oct 30, 2020 at 4:35 AM Francis Daly wrote:
> On Thu, Oct 29, 2020 at 11:42:11PM +0530, Kaushal Shriyan wrote:
>
> Hi there,
>
> > When I hit this URL http://219.11.134.114/test/_plugin/kibana/app/kibana
> on
> > the browser it does not get redirected to
> > https://vpc-lab-test-search-7h
Hi I am using nginx as a load balacer and I require sticky session (same
client always go to the same server), for this purpose I use this following
setup:
upstream backend {
ip_hash;
server host1:8000;
server host2:8000;
}
The `ip_hash` directive is what I learned f
All:
After reviewing the iptables chains workflow, I discovered that the Nginx
Worker (100.64.8.236:12345) outside interface was associated with the OUTPUT
chain.
(192.168.0.2:12345) OUTPUT ==>
(192.168.0.154:$po
