Why is my VPS’s guest IP different from its public connection address?
Some VPS platforms assign a public address directly to the guest; others map a public endpoint to a private guest address. The connection address can therefore differ from the address shown inside Linux. The provider’s service details define the actual model.
Instructions
1. Compare the assigned service information
Open the VPS Networking details and identify the addresses allocated to that server. Confirm whether access is direct, NAT-mapped or routed through another approved component. Do not add an arbitrary public address to the guest.
2. Inspect the guest’s current addresses and routes
These commands read the guest view only.
ip -brief address
ip route
ip -6 routeCompare interfaces and default routes with the documented network configuration. A private address can be correct behind an authorised mapping.
3. Check service exposure through the correct layer
For NAT-based access, the provider or network owner must map the required endpoint and port. A guest listener and firewall rule alone may not publish the service. For direct addressing, ensure the guest binds to an allowed address and retains the assigned route.
Check the result
- The guest and public address difference is explained by the documented service topology.
- Authorised access works through the assigned public or private endpoint.
Troubleshooting
- The public IP is absent from ip address
- It may be implemented by provider NAT; do not configure it locally without confirmation.
- Two guests appear to share an outbound address
- They may use shared egress NAT, which does not establish that unsolicited inbound access is available.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.