Hi All,
and then we found out that if we used HTTP Host Header as persistence
option, the web is doing fine, there is no captcha again to connect to
this website
Then we put the load-balancer into live-production environment (assuming everything is working good)
But, there goes another problem, the users feels it takes time to connect to their website now,
and when we try to put the KEMP aside (users connect to the server
without any load balancer between them), everything goes back to normal
We have a problem about SSL connection on KEMP...
We used LM-2200 (HA-mode)
actually, i'm gonna try to tell you all my problem in KEMP configuration,
At the first, we found a problem that the web shows a captcha every time
users try to connect, we try every aspect on KEMP configuration to solve
this,
users try to connect, we try every aspect on KEMP configuration to solve
this,
and then we found out that if we used HTTP Host Header as persistence
option, the web is doing fine, there is no captcha again to connect to
this website
Then we put the load-balancer into live-production environment (assuming everything is working good)
But, there goes another problem, the users feels it takes time to connect to their website now,
and when we try to put the KEMP aside (users connect to the server
without any load balancer between them), everything goes back to normal
Real servers use HTTP and on KEMP we used HTTPS connection (there is ssl certificate on KEMP)
Can anyone tell me what is going on with my configuration ?