Open PenguinzPlays opened 1 year ago
review iperf for udpate
~$ cat /etc/nginx/streams-enabled/proxy.conf server { listen 5201; proxy_pass perf; proxy_connect_timeout 5s; } server { listen 5201 udp; proxy_pass perf; proxy_connect_timeout 5s;
}
~$ cat /etc/nginx/conf.d/hosts.conf upstream perf { hash $remote_addr consistent; server 127.0.0.1:5202; # max_conns=1 fail_timeout=30s; server 127.0.0.1:5203; # max_conns=1 fail_timeout=30s; server 127.0.0.1:5204; # max_conns=1 fail_timeout=30s; server 127.0.0.1:5205; # max_conns=1 fail_timeout=30s;
}
upstream web { server 127.0.0.1:8081; # max_conns=3 fail_timeout=30s; server 127.0.0.1:8082; # max_conns=3 fail_timeout=30s; server 127.0.0.1:8083; # max_conns=3 fail_timeout=30s; server 127.0.0.1:8084; # max_conns=3 fail_timeout=30s; }`
`stream { log_format combined '$remote_addr -- [$time_local] $protocol $status $bytes_sent $bytes_received $session_time "$upstream_addr"'; access_log /var/log/nginx/stream.log combined; include /etc/nginx/conf.d/.conf; include /etc/nginx/streams-enabled/;
}`
Running into this error at the moment, researched how this is meant to work... 2023/07/19 06:05:39 [emerg] 151#151: the invalid "proxy_pass" parameter in /etc/nginx/nginx.conf:66
Migrate to utilizing Pomerium Open Source for routing and load balancing - update docs and steps to use this instead of NGINX
Setup server to enable cluster configuration allowing a single NGINX? LB / Proxy to forward to internal server with sticky connections based on load.