Vultr DocsLatest Content


Update

Updated on 07 November, 2025

Updates configuration settings for an existing Vultr load balancer including forwarding rules, health checks, and SSL certificates.


The vultr-cli load-balancer update command modifies existing load balancer configurations, allowing users to adjust settings such as protocols, algorithms, or SSL certificates without creating new resources.

Usage

console
$ vultr-cli load-balancer update <Load Balancer ID> [flags]

Examples

console
# Full example
$ vultr-cli load-balancer update 57539f6f-66a2-4580-936b-d0af934bce5d --label="Updated Load Balancer Label" \
--balancing-algorithm="leastconn" --unhealthy-threshold=20

# Shortened example with aliases
$ vultr-cli lb u 57539f6f-66a2-4580-936b-d0af934bce5d -l="Updated Load Balancer Label" -b="leastconn" -u=20

# Full example with attached VPC
$ vultr-cli load-balancer update 57539f6f-66a2-4580-936b-d0af934bce5d --vpc="bff36707-977e-4357-8f30-bef3339155cc"

Flags

Shorthand Long Version Description
-b --balancing-algorithm (optional) balancing algorithm that determines server selection | roundrobin or leastconn
-c --check-interval (optional) interval between health checks.
- --cookie-name (optional) the cookie name to make sticky.
- --firewall-rules (optional) a comma-separated, key-value pair list of firewall rules. Use - between each new rule. E.g: "port:80,ip_type:v4,source:0.0.0.0/0-port:8080,ip_type:v4,source:1.1.1.1/4"
-f --forwarding-rules (optional) a comma-separated, key-value pair list of forwarding rules. Use - between each new rule. E.g: "frontend_port:80,frontend_protocol:http,backend_port:80,backend_protocol:http-frontend_port:81, frontend_protocol:http,backend_port:81,backend_protocol:http"
- --global-regions (optional) Deploy the load balancer across multiple global regions.
- --healthy-threshold (optional) number times a check must succeed before returning to healthy status.
- --http-version (optional) Set HTTP version. Use 2 for HTTP2 or 3 for HTTP3. HTTP3 requires HTTP2 to be enabled.
-i --instances (optional) an array of instances IDs that you want attached to the load balancer.
-l --label (optional) the label for your load balancer.
-n --nodes (optional) The number of nodes to add to the load balancer (1-99), must be an odd number
- --path (optional) HTTP Path to check. only applies if protocol is HTTP or HTTPS.
- --port (optional) the port to use for health checks.
- --protocol (optional) the protocol to use for health checks. | https, http, tcp
-p --proxy-protocol (optional) if true, you must configure backend nodes to accept Proxy protocol.
-t --response-timeout (optional) timeout before health check fails.
-s --ssl-redirect (optional) if true, this will redirect HTTP traffic to HTTPS. You must have an HTTPS rule and SSL certificate installed on the load balancer to enable this option.
- --timeout (optional) The maximum time allowed for the connection to remain inactive before timing out in seconds.
-u --unhealthy-threshold (optional) number times a check must fail before becoming unhealthy.
-v --vpc (optional) the VPC ID to attach to your load balancer.

Comments