Nice, hadn’t noticed the port range capability.
The proxy_pass and just directly referencing the ip would make it nice and
concise. Unfortunately I am wanting to balance across multiple backends,
but this is all good to know come different requirements.
Cheers
On Mon, Mar 2, 2020 at 2:02 PM Rein
> I get that the NGINX listen statement works on an individual port basis, so
> the equivalent of what's below in NGINX would at the very least require 300
> listen statements.
You can listen on a port range (see below).
> FYI I've tried referencing my own declared variables from within the u
Hi,
We are using Nginx Web server on CentOS Linux release 7.7.1908 (Core)
*OpenSSL Version*
#openssl version
OpenSSL 1.0.2k-fips 26 Jan 2017
#
*Nginx Version*
#rpm -qa | grep nginx
nginx-1.16.1-1.el7.x86_64
#
Can someone please suggest me to use strong cipher suites for SSL/TLS
encryption. Tha
> but my agents are still unable to send logs over port 1514 UDP
Well at least the nginx setup seems in working order.
Now do you see any more detailed messages on the agents (like extended ip/port
info / connection error)?
Also you could inspect the network traffic to see if the centos box re
Hi
So far from my reading and testing of NGINX I can't find a compact way of
configuring NGINX as I've done here with HAProxy config. Disregard the bind on
a port range,
I get that the NGINX listen statement works on an individual port basis, so the
equivalent of what's below in NGINX would at
Hi.
i've changed the configuration:
stream {
upstream master {
server 10.0.0.7:1515;
}
upstream mycluster {
hash $remote_addr consistent;
server 10.0.0.7:1514;
server 10.0.0.6:1514;
}
server {
listen 1515;
proxy_pass master;
}
