On Mon, Aug 31, 2020 at 06:15:00AM -0400, Dr_tux wrote:
> Hi, I have 2 turn server. I would like to use Nginx for load balancer them.
> But I have a problem. When I use the AWS ELB it works perfectly. If I try
> with Nginx, I got an error.
> Remote addr should be client_ip. Nginx, send itself IP address to coturn
On Wed, Sep 02, 2020 at 01:08:43AM -0400, Dr_tux wrote:
> When I add the proxy_bind parameter, requests are never forwarded to the
> server behind.
Is there any hint in your nginx logs of what is happening?
For example, on one old system here, when I test the config as root,
I can see:
# sbin/nginx -t
nginx: [emerg] transparent proxying is not supported on this platform, ignored in /usr/local/nginx/conf/nginx.conf:240
nginx: the configuration file /usr/local/nginx/conf/nginx.conf syntax is ok
nginx: configuration file /usr/local/nginx/conf/nginx.conf test is successful
and when I try to connect to my nginx udp port from a remote machine,
I see no hint of the request being forwarded; but I do see a [crit]
message in the nginx error log, of the form "bind(client ip) failed
(99: Cannot assign requested address) while connecting to upstream"
When I try to connect from the local machine, I do see the request being
forwarded, with the same source address as my original packet used -- the
192.168.x one, or the 127.0.x one. So proxy_bind is being attempted, and
my operating system setup is preventing the "external" address being used.