Page 1 of 1

vicidial webserver cluster

PostPosted: Thu Feb 27, 2020 2:42 am
by vijo
Hai everyone,

I have vicidial servers (astguclient version 2.14) installed. Which needs to do the cluster configuration.

I have done the clustering of 5 Severs. Which are below.

DB server 1 Server.
Asterisk 2 Server
Webserver 2.

Now I have a domain name like vicidial.com which the agents will access on the agent page and i need to balance the web load into the webserver.

But my webservers are in local address and i have configured the apache load balancer to load web load. My domain name is routed to load balance and from the load balancer, it's redirecting to webserver1 and webserevr2. But while redirecting to its showing local IP address. How I can avoid this?

Is there any vicidial web balancer or any other suggestions.

Re: vicidial webserver cluster

PostPosted: Thu Feb 27, 2020 9:25 am
by williamconley
You seem to have asked a question about an apache load balancer ... on a Vicidial forum. Perhaps you should ask that question on an Apache forum? I would also recommend posting more detail about the load balancer, such as settings and configuration options.

Re: vicidial webserver cluster

PostPosted: Thu Feb 27, 2020 8:07 pm
by roger.milligan
Hello Vijo

You are not the first to have this requirement, but please clarify - where are you wanting to see the user's IP address rather than the load balancer's? If it's in the ViciDial logs then that may require a custom change to ViciDial (to look at $_SERVER["HTTP_X_FORWARDED_FOR"]), but if you are wanting it in the Apache access_log or similar, you may be able to get it by changing the log format to include mod_remoteip or X-Forwarded-For (will require some research depending your setup).

What load web balancer are you using? - if it's something like HAProxy, there are further settings to explore like "option forwardfor" ( See: http://cbonte.github.io/haproxy-dconv/1 ... forwardfor )

Roger

Re: vicidial webserver cluster

PostPosted: Thu Feb 27, 2020 11:47 pm
by williamconley
where are you wanting to see the user's IP address rather than the load balancer's?

His problem is that the system is using the local ip rather than the public IP. Not useful if the agents in question are unable to access on the local subnet.