Networking
View IP addresses and network interfaces Devpilot detects on your server.
Networking
The Networking tab shows the network configuration Devpilot has detected on your server. It is primarily a read-only view — Devpilot reports what the server is actually configured with, gathered from the management agent.
What You'll See
Open Servers, select a server, and click Networking. The page displays:
- Public and private IP addresses — Values Devpilot has on file for the server, along with any additional addresses detected on the machine's network interfaces.
- Network interfaces — Per-interface information (for example
eth0,ens3,lo), including interface status. - Recent throughput — Upload and download rates from the monitoring agent, so you can see at a glance whether the server is moving traffic right now.
For provisioned servers, Devpilot also shows the primary public and private IP it recorded during provisioning.
Changing Network Configuration
Devpilot does not edit routing tables, bind additional IPs, or reconfigure network interfaces for you. If you need to change the actual network configuration on the server, you have two options:
- Use your cloud provider's console. Attach/detach secondary IPs, elastic IPs, or floating IPs through the provider. Devpilot picks up the new address when the agent next reports.
- Use the Web Terminal or a Script to change configuration directly on the server (for example editing
netplanorNetworkManagerprofiles, or usingipcommands).
Be careful when reconfiguring networking over SSH. A mistake can drop the SSH session and the server from the network. Keep provider console access available as a fallback.
Firewall
Network-level access control is handled by the server firewall on the Security tab. From a networking perspective, that's where you decide which ports accept traffic and from which sources. See Security — Firewall Management.
If your server sits behind a load balancer that you manage yourself or through your cloud provider, configure the server firewall to accept application traffic only from the load balancer's IPs, and block direct public access to the application port.