FuguHub Your Personal File Sharing Solution



Manage Data Your Way

The Barracuda HTTPS Tunnel

Note: The following is for our old tunnel technology. We recommend that all users use the new and much faster MxTunnel.

The Barracuda HTTPS Tunnel acts as a SOCKS, HTTP, and HTTPS proxy server. The HTTPS Tunnel allows you to use your Internet applications such as your browser anonymously, despite firewalls. The Barracuda HTTPS Tunnel also supports a direct tunnel for protocols that do not support proxying; such as TELNET, FTP, VNC, and most Internet protocols.


See our SSL VPN solutions for a gentle introduction.

Interactive tunnel overview:

Tunnel overview

Free Software

The Barracuda HTTPS Tunnel Client is a free and complementary FuguHub product. The Barracuda HTTPS Tunnel Client connects and establishs a secure tunnel to the HTTPS Tunnel Server integrated into the FuguHub Web Server.


We provide three versions of the HTTPS tunnel client:

  • The Java Web Start version is integrated into the FuguHub Web Server. This version is started directly from the FuguHub Web Server. The Java Web Start version usually inherits proxy settings from the browser and will automatically authenticate with any company firewall/proxy.
  • The command line version is useful for automating tasks and is ideal for embedding into scripts and DOS batch files. Download Windows version. Download generic Java version.
  • The GUI version is identical to the command line version, except for that it uses a graphical console. Download Windows version. Download generic Java version.

* The HTTP tunnel clients require a deployed FuguHub server.

Testing the HTTPS Tunnel

The following is a quick guide on how to get started with the HTTPS tunnel.

You should see the following if you start the tunnel without any parameters:

Barracuda HTTPS Tunnel Client version 2.3 (C) Copyright 2006-2007 Real Time Logic. Usage: HttpsTunnel [options] <remotehost> <tunnels> where possible options include: -ssl <host:port> Use SSL proxy. Ex: -ssl companyproxy:8080 -socks <host:port> Use SOCKS5 proxy. Ex: -socks companyproxy:1080 -nocomp Do not use compression -user <user> user name -pass <password> password <tunnels> ::= <tunnel | http | socks>+ <tunnel> ::= <t:[localaddress:]localport:remotehost:remoteport> <http> ::= <h[p]:[localaddress:]localport> <socks> ::= <s[p]:[localaddress:]localport> Localaddress: Optionally bind to a local address such as 'localhost'. Localport: The local server listen port. Remotehost: A hostname/ip address reachable from the FuguHub server. Remoteport: The destination port number. Examples: A VNC server and the FuguHub server are running on the same computer. myhomecomputer.net t:5900:localhost:5900

The HTTPS Tunnel supports the following protocols:




HTTPS tunnel


The tunnel is typically used by clients that do not support a proxy such as telnet, ftp, VNC, etc..

HTTP proxy


The HTTP proxy can be used by clients that only support standard HTTP proxy. The FuguHub HTTPS Tunnel supports only HTTP 1.0 connections. Avoid using this proxy if your client supports HTTPS and/or SOCK5.

HTTPS proxy


This protocol is also called a web tunnel and provides an efficient tunnel for clients that support this protocol. The tunnel is established by a client by sending the HTTP CONNECT method.

SOCK5 proxy


The FuguHub HTTPS Tunnel supports the SOCKS version 5 protocol. The FuguHub HTTPS Tunnel does not support UDP connections.

The following example shows:

  • How to establish a HTTP/HTTPS proxy on port 8080.
  • A SOCKS proxy on port 1080 that only accepts connections from localhost.
  • A VCN tunnel to a VCN server running on the same computer as the FuguHub Web Server. The tunnel client is also configured to only accept connections from localhost.

From the command prompt:
HttpsTunnel mycomputer.com hp:8080 s:localhost:1080 t:localhost:5900:localhost:5900

Connections established over the HTTPS Tunnel Client are by default authenticating with the FuguHub Web Server using the user ID you entered when starting the HTTPS Tunnel Client. It is suggested that you bind the tunnel client listen port to "localhost" to prevent other users on your current network from using your tunnel and/or proxies. We do this in the above example with the SOCKS proxy and the VNC tunnel.

The HTTP, HTTPS, and SOCKS5 proxies can optionally ask the client to authenticate. This is done by providing the 'p' attribute as shown above when establishing a HTTP/HTTPS proxy. The HTTPS tunnel client will then forward the login request from the client down to the FuguHub Web Server. The HTTPS Tunnel Client redirects the authentication handshaking down to the FuguHub Web Server. Not all clients support authentication. As an example, browsers typically support authentication using HTTP/HTTPS proxies, but not using SOCKS proxies.

Use Cases