1Add one
In the console, go to Deploy and choose Or a load balancer, or use Load balancers on the Overview. Pick the location where your servers are. It's ready in a few minutes.
In the console, go to Deploy and choose Or a load balancer, or use Load balancers on the Overview. Pick the location where your servers are. It's ready in a few minutes.
Open Settings on the load balancer:
Tick the servers it sends traffic to, up to 25, at the same location. It lets itself through their firewalls; nothing else changes on them.
Add an A record for your domain with the load balancer's IPv4 address (and AAAA with its IPv6 address, or none). Then enter the domain under Settings. Until then, its free hostname works.
The certificate is issued once the domain points at the load balancer, and renews by itself.
Every few seconds it asks each server for a page (/ unless you set another under Advanced), or opens the port for TCP. A server that fails three times in a row gets no traffic until it answers twice. The page shows each server as Up or Down.
For web traffic, your servers see the visitor's address in the X-Forwarded-For header and the original scheme in X-Forwarded-Proto. For TCP, they see the load balancer's address.
Everything here is also in the API (/load-balancers), the eh load-balancers command, Terraform (entityhosting_load_balancer) and the AI assistant tools.