SSH TUNNELS / PORT FORWARDING

Bring remote services within reach over SSH.

Keep port-forwarding configurations alongside the server connection instead of maintaining a separate collection of one-off terminal commands.

Actual ShadeTerm port-forwarding setup fields for local port, destination host and remote port — Configure an SSH tunnel

SSH tunnel workflowsUseful for internal web toolsConnection-scoped setup

01 / WHY IT MATTERS

Port forwarding turns an SSH connection into a controlled route to a service you cannot or should not expose publicly.

ShadeTerm keeps your tools focused on a connection and the task you are doing — rather than adding more windows and manual steps.

01 / FEATURE

Reach internal services

Use a tunnel when a database, admin interface or private development server listens only on an internal address.

02 / FEATURE

Keep forwarding tied to its host

Manage the connection and related forwarding settings as part of the server profile rather than rediscovering command-line flags.

03 / FEATURE

Stay intentional about access

A tunnel is not a security policy by itself. Keep listeners restricted to the right interface and users.

SEE IT IN SHADETERM

Set up and use an SSH tunnel.

Screens from ShadeTerm for Windows — the interface behind the workflow.

Real ShadeTerm state or terminal showing the created forwarding connection — Use your forwarded connection

02 / IN PRACTICE

How this fits your server workflow.

Designed around everyday developer tasks, not a dashboard of features you never use.

A practical example: localhost to your server

A typical local tunnel maps a port on your computer to a service reachable from the SSH server. With OpenSSH, the equivalent pattern is ssh -L 8080:127.0.0.1:8080 user@server.

The example command is explanatory; the exact UI and supported tunnel modes should be confirmed in your current ShadeTerm build before publishing a feature claim.

Inspect the destination, not just the port

A green connected state is not proof that the service behind the tunnel is reachable. Test the local endpoint and confirm that the remote application is listening.

Be especially careful about binding a tunnel to 0.0.0.0 on a shared machine. Local-only binds are safer for most development tasks.

03 / WORKFLOW

From connection to result.

A focused sequence you can follow in your own ShadeTerm workspace.

01 / STEP

Choose a host

Open the saved SSH connection for the target network.

02 / STEP

Set a route

Configure the forwarding endpoint in the connection settings.

03 / STEP

Test access

Connect and verify the local endpoint before using the service.

04 / DETAILS

Common questions.

Practical limitations and useful details before you get started.

Does port forwarding require changing the application server?

A tunnel needs an SSH server that permits forwarding and a reachable destination; many tasks do not require exposing a public service port.

Is tunneling the same as opening firewall access?

No. The traffic path and access boundaries differ; do not assume one grants the other.

Can every SSH server allow forwarding?

No. Server administrators can restrict it with SSH configuration and policy.

Explore related featuresSSH Jump Host ↗ SSH Terminal ↗ Connection Profiles ↗

ShadeTerm / WINDOWS

Work with your server, not around your tools.

Terminal, files, code and more — organized around your SSH connections.

Try ShadeTerm