Hubfly spaceDocs
Console

Box · Guide

Box networking and exposure

Connect guest interfaces, expose HTTP or raw ports, and understand when a static IP is useful.

How traffic reaches a Box

A Box lives on managed private networking. Public access is an explicit route through an HTTP domain or a TCP/UDP port mapping.

  • HTTP domain: public hostname → Hubfly space HTTP proxy → selected Box guest port. Use this for a web service and confirm that your process listens on the guest interface.
  • Port mapping: assigned public host port → a selected NIC and guest TCP or UDP port. The platform chooses the public host port; the API request selects the guest port.
  • Firewall policy remains in force. Publishing a route adds the narrow required inbound exception, but guest firewall settings can still block traffic.

Interfaces and private traffic

Each Box starts with a primary managed NIC. Additional NICs can be attached, and NIC records expose the IDs needed by mappings and static IP actions.

  • Select the correct NIC when adding a port mapping or attaching a purchased IP. Removing a NIC can interrupt routes and guest connectivity.
  • Private Box-to-Box traffic and console access are separate from public WAN traffic. Check guest routes and interface names when an application binds only to localhost.

Publish a web app

Create an HTTP domain with a subdomain and targetPort. The API returns the hostname and URL; the domain can later be retargeted or removed.

  • Wait for the domain route to become ready, then test its URL. The target application must listen on the chosen guest port.
  • HTTP domains are the simplest path for web traffic. Use a raw port mapping for non-HTTP protocols or when an application specifically needs TCP or UDP.

Static IP and direct ports

A static IP is a separate regional project resource with purchase, attach, and detach actions. The API reports inventory and assignment state.

  • Review the displayed purchase price before confirming. Buying an IP and attaching it to a NIC are separate steps.
  • Port mappings are managed routes. Read the mapping after its operation succeeds to find its assigned public endpoint; do not assume guestPort is also the public port.

Automating this workflow

See the matching Box API endpoints for exact request fields and response schemas. Host operations can continue after an API request returns.

Back to the Box guide · All Box API groups

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top