How to Manage Forwarding Rules on a Vultr Load Balancer

1 min readUpdated 23 October 2026

Map Vultr Load Balancer frontend ports to backend ports over HTTP, HTTPS, TCP, or UDP. HTTPS needs a certificate.

Forwarding rules on a Vultr Load Balancer define how incoming traffic is directed to your backend servers. These rules allow you to specify a protocol, port, and target protocol/port for routing requests. By configuring forwarding rules, you can manage and optimize how traffic is distributed, enhancing the performance and accuracy of your load balancing setup.

Follow this guide to manage forwarding rules on a Vultr Load Balancer using the Vultr Console, API, CLI, or Terraform.

Navigate to Products and click Load Balancers.
Click your target Load Balancer to open its management page.
Scroll down to Rules and click the pencil icon in the Forwarding Rules section.
Verify, modify, or click Add to create a rule.
Set the LB Protocol / Port and Instance Protocol / Port.
- HTTP: Forwards traffic using the Hypertext Transfer Protocol (HTTP).
- HTTPS: Forwards traffic using the Hypertext Transfer Protocol Secure (HTTPS). Enabling HTTPS rules requires an SSL certificate linked to the Vultr Load Balancer instance.
- TCP: Forwards traffic using the Transmission Control Protocol (TCP).
- UDP: Forwards traffic using the User Datagram Protocol (UDP). Ideal for latency-sensitive applications such as DNS, VoIP, gaming, and streaming.
Save the changes.

0 Comments

Start the conversation

Be the first to comment and share your perspective with the community.

Add and Remove Forwarding Rules on a Vultr Load Balancer | Vultr Docs