Remote access to your own server without a public IP: how it works and why it's safe
You have a machine with no public IP — a home PC, an office server, or a rented rig behind NAT. You can't reach it from outside: the ISP gave you no external address, and router port-forwarding is fiddly and risky. Remote Access solves this with one command: you reach your own server over SSH or RDP through our hub — from anywhere.
How it works
The key idea: the connection is always outbound. Your machine itself opens a secure channel to our hub (a relay node) and keeps it alive. Nothing on your side listens to the internet: no public IP, no port forwarding, not a single exposed port. When you need in, you reach your server through the hub as if it were right next to you.
- You run one command on the server — it brings up an encrypted outbound tunnel.
- The channel is initiated by the machine itself (outbound), so it works behind NAT, routers and firewalls.
- You connect to your server through the hub — over SSH or RDP, or right in the browser.
Why it's safe
- Nothing is exposed — only an outbound channel. No open ports, no public IP, no forwarding: the server isn't hanging out on the internet.
- Client isolation: everyone gets a separate channel; you can reach only your own servers, never anyone else's.
- Encrypted throughout — traffic runs over SSH, modern cryptography end to end.
- Per-connection keys, scoped: each connection uses its own keys, and service access is limited to service functions only.
- You stay in control: disable the service any time with one command — it fully removes the tunnel and the service account from your machine.
- Transparency: the channel status is visible in your account, and nothing happens without the install command you run.
How to start
It's simple and takes a couple of minutes:
- Sign up or log in — by e-mail or via Telegram.
- Open the “Remote access” section.
- Take a trial server for free or get a subscription.
- Copy the install command and run it on your server (Linux, with sudo) — nothing else to configure.
- Wait for the “online” status — usually a few seconds.
- Connect: the “Terminal” button right in the browser, or the “Connection kit” for SSH from your computer.
# одна команда установки на вашем сервере (точную ссылку берите в кабинете)
curl -fsSL https://vast.sale/remote/dl/ВАША-ССЫЛКА -o podkl.sh && sudo bash podkl.sh
Managing and detaching
- Status, renewal and payment — in your account, the “Servers” tab.
- Auto-renewal from balance — optional and with explicit consent.
- Detach any time: one command fully removes our tunnel and the service account from your machine.
# полностью удалить служебный доступ с вашего сервера
sudo vast-service-remove