Why can I open the VPS console but not connect with SSH?
A provider console is an alternate management path to the guest’s screen or terminal. It can work even when the guest’s public network, firewall or SSH service is unavailable. Console access therefore does not prove that SSH is reachable.
Instructions
1. Confirm the console belongs to the intended server
Use Britixo’s Access tab and the generated authorised console information where available. Treat temporary links or credentials as private and observe any displayed expiry.
2. Inspect guest networking and listeners
From the Linux console, read the current configuration.
ip -brief address
ip route
sudo ss -lntpCompare the assigned addresses, default route and SSH listener with the provider’s networking details. Do not infer public reachability from a loopback-only listener.
3. Test from the Windows client
Use the actual SSH port, then compare guest firewall and provider-layer restrictions.
Test-NetConnection 203.0.113.10 -Port 22The TCP result tests the external access path from this client. Keep the console available while diagnosing a narrowly identified cause.
Check the result
- The guest has the intended addresses, route and SSH listener.
- An authorised external SSH session succeeds while the independent console remains available.
Troubleshooting
- The guest shows only a private address
- The service may use NAT or another assigned public-access model; use its actual connection details.
- The console works but the guest is still booting
- Check first-boot status and service logs before changing networking.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.