Wow, was struggling with that for a week already.
Can’t believe that was it.
Thank you Valentin and Francis!
> Op 15-dec.-2015, om 12:26 heeft Valentin V. Bartenev het
> volgende geschreven:
>
> On Tuesday 15 December 2015 11:56:43 Bram wrote:
>> Problem is that it will not accept anything be
On Tuesday 15 December 2015 11:56:43 Bram wrote:
> Problem is that it will not accept anything besides $remote_addr and
> $request_uri.
> For example:
>
> upstream loadbalancer {
> hash $server_name consistent:
There's a typo: you've used a colon at the end of the directive.
wbr,
On Tue, Dec 15, 2015 at 11:56:43AM +0100, Bram wrote:
Hi there,
> Problem is that it will not accept anything besides $remote_addr and
> $request_uri.
> For example:
>
> upstream loadbalancer {
> hash $server_name consistent:
Use ; not :
> #hash $request_uri consistent;
>
Problem is that it will not accept anything besides $remote_addr and
$request_uri.
For example:
upstream loadbalancer {
hash $server_name consistent:
#hash $request_uri consistent;
server 10.0.0.1:8080;
server 10.0.0.2:8080;
}
Will fail with:
invalid numb
On Tuesday 15 December 2015 10:13:35 Bram Verdonck wrote:
> Hi all,
>
>
> I wish to use load balancing in front of a shared webhosting cluster with
> multiple domains.
> To make optimal use of resources, it would make sense to do load balancing
> based on domain instead of random or based on IP
Hi all,
I wish to use load balancing in front of a shared webhosting cluster with
multiple domains.
To make optimal use of resources, it would make sense to do load balancing
based on domain instead of random or based on IP.
I noticed that there is a hash parameter but I’m unable to use $server
