Local SSH Tunnel Setup for Windows
These instructions only need to be followed the first time. Once you have your tunnel information saved you can simply start the tunnel and connect.
To connect to your SSH tunnels from Windows we recommend using PuTTY. Once you have configured PuTTY and created a tunnel you can leave it open for as long as you want. If it becomes disconnected, you can simply reconnect.
Note! If you have Windows 10 built in SSH enabled you can follow the same instructions for macOS/Unix.
The port you choose locally can be changed (see Notes). If you are tunneling into many hosts using different services, you find it useful to pick a generic port and create a tunnel and leave it open. Each service you use locally can just be configured to use that port and you don’t need to often change it.
Note! the images below will not have your account information in them! Please use the account information Virtyx provides.
Download and install PuTTY if you don’t already have it installed.
To start, type in the basic connection information.
Type in the server you’ve been assigned and keep the port at the default
The server will be something similar to
boring1.virtyx.com. It is highly
recommended to type in a name under “Saved Sessions” so you don’t need to do
this setup again.
Next, go to Connections > Data:
Type in your username for Auto-login username. It will look something like
Note! This step is technically optional, but saves typing it in each time later.
Next, go to Connections > SSH:
Check the box Don’t start a shell or command at all. This is the same as
-N option on Unix systems and is required.
Next, expand the SSH section and go to Tunnels:
The forwarded port needs to be setup. This will allow you to connect to “localhost” on your computer and forward your traffic through the Virtyx Cloud to the target host.
The Source port should be the port you want to connect to locally. Normally
this will be the same as remote port for the service you’re using. However this
can be something else if you have a conflicting service running already. For
example, if you are connecting to VNC on the host, you would type in
The Destination is where this tunnel sends the traffic. This is the Virtyx
Cloud. This port has been specifically assigned to your user and no other port
will work here. The host will always be
localhost as well. For example, if
your user was assigned port
4500, you’d type in that combination:
Make sure you press “Add” and verify the configuration is now listed in the box.
Go back to Sessions and click save to update your configuration. When ready to connect, click Open.
The first time you will be asked to verify the host. It is safe to press Yes. In the window that pops up you can type (or paste), your password to connect to the server. This is the password given to you upon setup of your tunnel account. If you lose this password please contact firstname.lastname@example.org and we will reset it. Once connected, the connection will appear to “hang” - it won’t do anything. No command is being run and no shell will be presented. This is normal, the tunnel has been opened and will simply stay that way until you close the window.
Finally, you can configure whatever software you are using to connect to your
tunnel. You do this by connecting to
localhost and specifying the first
port you typed in above, in this example,
You may run into a conflict on the local port. For example, if you wanted to VNC
into the target host, the setup would use port
5900 for local forwarding.
However, if you have a VNC server running on your own computer on that port,
there will be a conflict. To resolve, simple pick a different port on your local
Using your VNC software to connect, you would then use
of the default port