Skip to main content

Port Forwarding

⏱️ Estimated reading time: 5 minutes

What is Port Forwarding?​

Port Forwarding is a networking technique that enables external traffic on a specific port to be directed to an internal service or virtual machine. When configured, traffic coming to a public IP on a specified public port is forwarded to a private port on a target instance within your network.

Common use cases include:

  • Web servers (HTTP/HTTPS)
  • SSH and RDP access
  • Application-specific ports (e.g., database access, game servers)

Port Forwarding provides flexibility for remote access and service exposure, while also allowing you to maintain internal network isolation and control over open ports.

Accessing Port Forwarding Settings​

You can manage Port Forwarding rules in two ways on the Webberstop Cloud Portal:

Option 1: Via the Network Menu​

  1. Navigate to Networks from the sidebar.

  2. Select the Public IP Address tab.

  3. Locate your instance’s assigned public IP and click Port Forwarding.

Option 2: Via VM Settings​

  1. Go to the Instances section in the portal.

  2. Choose the instance you want to configure.

  3. Open the VM Settings tab.

  4. From the sidebar, click Port Forwarding to manage the rules for the instance’s public IP.

Viewing Port Forwarding Rules​

Once inside the Port Forwarding Management Panel, you’ll see a list of all active port forward rules associated with the selected public IP. Each rule defines:

  • Public Port → the external port exposed to the internet
  • Private Port → the internal port on the VM
  • Protocol → TCP or UDP
  • Target VM → the instance receiving the traffic

Adding a Port Forwarding Rule​

To configure a new port forward rule:

  1. Click the ➕ Add Rule button in the top-right corner.

  2. Complete the form with the following:

    • Public Port: The external port exposed to incoming traffic (e.g., 8080).
    • Private Port: The internal port on the VM where traffic will be redirected (e.g., 80).
    • Protocol: Select TCP or UDP depending on the service.
    • Select VM: Choose the instance that will receive the forwarded traffic.

  3. Click Save to apply the rule.

The new rule will now appear in the list and become active immediately.

Best Practices​

  • Only open necessary ports to reduce attack surface.
  • Use non-default public ports (e.g., 2222 for SSH) when possible for added security through obscurity.
  • Combine Port Forwarding with Firewall Rules to restrict access by IP or CIDR.
tip

If you're exposing a service to the internet, ensure the corresponding firewall rules are in place to allow traffic on the specified public port.