| We moved this page to our Documentation Portal. You can find the latest updates here. |
Issue
I cannot login to my Loadbalancer WebUI
Environment
OnApp 5.x and up
Answer
Manual changes to a loadbalancer configuration cannot be supported by OnApp. OnApp will put in place the necessary configuration for the base Load Balancing functionality offered by the OnApp UI when creating or editing a Load Balancer.
Additional Info
In most cases, the Load Balancer will build and configure on its own and the ports will work. If there is some problem with the cluster nodes not responding, the configuration on the backing virtual servers may need to be checked - see "ARP problem" in the loadbalancer.org docs: (http://pdfs.loadbalancer.org/quickstartguideLBVMv7.pdf)
Please note: Default credentials for load balancers are changed upon LB creation, all management of load balancers should be done through OnApp UI.
OnApp uses Layer 4 / DR mode of the LB exclusively.
Comments
1 comment
There are two features of the LB that are really poor at the moment. The first is that it does not support NAT configurations. So if you would like to load balance instances in OnApp ALL of those instance must have public IP addresses. The second is that the current configuration does not support different port configurations. You can not have port 80 of your IP balance one pool and port 443 balance another.
OnApp needs to get on fixing this ASAP.
Please sign in to leave a comment.