Network

Documentation Index

Fetch the complete documentation index at: https://docs.suji.fr/llms.txt

Use this file to discover all available pages before exploring further.

The Network tab shows your VM’s public-facing addresses and its outbound/inbound traffic for the current billing month.

​

Public addresses

Each row has a one-click Copy button.

​

How traffic is counted

• Outgoing — bytes leaving the VM in the current billing month.
• Incoming — bytes arriving at the VM in the current billing month. Free — never counts toward your quota.
• Quota — your plan’s monthly included outbound. Overage may be billed by the cloud provider depending on size.

Units use the same convention the cloud provider does internally (a “20 TB” included quota is 20 × 1024⁴ bytes).

​

Resetting / billing cycle

The traffic counters reset on the first of the calendar month, matching the cloud provider’s billing cycle.

​

The tunnel

Every Suji VM ships with cloudflared running as a system container. It:

• Holds a long-lived authenticated connection out to Cloudflare’s edge.
• Receives inbound HTTPS for the hostnames in its ingress rules.
• Forwards requests to your apps via localhost:<port> inside the VM.

You don’t manage cloudflared directly. Suji updates its ingress rules every time you install / upgrade / uninstall an exposed app.

​

Why use the tunnel hostname instead of the public IP?

• TLS: the tunnel terminates valid certificates for *.suji.fr automatically.
• No direct exposure: your app doesn’t have to open a public port — cloudflared connects out, not in.
• DDoS protection: Cloudflare absorbs typical noise.

Direct IP access (e.g. running curl https://1.2.3.4) won’t reach your apps because the apps don’t bind public ports. They listen only on localhost inside the VM’s network namespace.

​

Next