Sample code for 30+ languages & platforms
PHP

SSH Tunnel with Dynamic Port Forwarding

See more SSH Examples

Demonstrates how to start a background thread that runs a portable SSH tunnel w/ dynamic port forwarding that the foreground thread can use for establishing connections through an SSH tunnel.

Chilkat PHP Downloads

Chilkat2 PHP
<?php

use Chilkat2\Http;
use Chilkat2\SshTunnel;

$success = false;

// This example assumes the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.

$success = false;

$tunnel = new SshTunnel();

$sshHostname = 'sftp.example.com';
$sshPort = 22;

// Connect to an SSH server and establish the SSH tunnel:
try {
    $tunnel->Connect($sshHostname, $sshPort);

    // Authenticate with the SSH server via a login/password
    // or with a public key.
    // This example demonstrates SSH password authentication.
    $tunnel->AuthenticatePw('mySshLogin', 'mySshPassword');

    // Indicate that the background SSH tunnel thread will behave as a SOCKS proxy server
    // with dynamic port forwarding:
    $tunnel->DynamicPortForwarding = true;

    // We may optionally require that connecting clients authenticate with our SOCKS proxy server.
    // To do this, set an inbound username/password.  Any connecting clients would be required to
    // use SOCKS5 with the correct username/password.
    // If no inbound username/password is set, then our SOCKS proxy server will accept both
    // SOCKS4 and SOCKS5 unauthenticated connections.

    $tunnel->InboundSocksUsername = 'chilkat123';
    $tunnel->InboundSocksPassword = 'password123';

    // Start the listen/accept thread to begin accepting SOCKS proxy client connections.
    // Listen on port 1080.
    $tunnel->BeginAccepting(1080);

    // Now that a background thread is running a SOCKS proxy server that forwards connections
    // through an SSH tunnel, it is possible to use any Chilkat implemented protocol that is SOCKS capable,
    // such as HTTP, POP3, SMTP, IMAP, FTP, etc.  The protocol may use SSL/TLS because the SSL/TLS
    // will be passed through the SSH tunnel to the end-destination.  Also, any number of simultaneous
    // connections may be routed through the SSH tunnel.

    // For this example, let's do a simple HTTPS request:
    $url = 'https://www.ethereum.org/';

    $http = new Http();

    // Indicate that the HTTP object is to use our portable SOCKS proxy/SSH tunnel running in our background thread.
    $http->SocksHostname = 'localhost';
    $http->SocksPort = 1080;
    $http->SocksVersion = 5;
    $http->SocksUsername = 'chilkat123';
    $http->SocksPassword = 'password123';

    $http->SendCookies = true;
    $http->SaveCookies = true;
    $http->CookieDir = 'memory';

    // Do the HTTPS page fetch (through the SSH tunnel)
    $html = $http->QuickGetStr($url);

    // Stop the background listen/accept thread:
    $waitForThreadExit = true;
    $tunnel->StopAccepting($waitForThreadExit);

    // Close the SSH tunnel (would also kick any remaining connected clients).
    $tunnel->CloseTunnel($waitForThreadExit);
} catch (\Chilkat2\Exception $e) {
    echo $e->getMessage(), "\n";
    exit;
}