This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]


Go to the server preferences, and select tunnels.

Create a new tunnel, using the HTTP(S) Tunnel type. Enable Auto start, and Use Chunked Encoding. The name is not important, but something simple will do.

The local client port must be 55555. That is five fives.

The destination host must be, and the destination port can be anything as it will be ignored for this configuration.

Set the in Channels, and out Channels to be an appropriate multiplier for the speed gain you are looking for. You want to use the smallest value possible that still gives you the performance you need. I usually suggest something around 10 to 20. The min should be 1, and the max should be between 10 and 20. Enable the Auto checkbox on both as well.



Next, go to the IP / Servers tab in the server preferences. Add two new server port items. The first on 55521 (FTP), and the other on 55580 (HTTP). Both should have their IP set to, and have the User Connection Group set to the same value as your main server's HTTPS ports value.

These ports, their protocol, and IPs must be set as defined. They will be used internally as part of the tunnel process. They must be FTP and HTTP respectively. They will be tunneled over the secure HTTPS tunnel.



Open the user manager, and select your user you want to allow to use the accelerated tunnel. Grant them access to that tunnel.


At this point, you can login and use the WebInterface and start getting the accelerated speeds.


The FTP protocol can also be sent over the HTTPS encrypted tunnel and get the same speed gains as the WebInterface's automatic Java applet handling. To do this, we use a java web start application that can start and stop the tunnel for a local FTP client to connect through.

We make a dummy user named "tunnel" that has no access to anything, other than the ability to login, and startup a secure tunnel.


Now you can use a URL like this in your web browser to download and start the tunnel for the FTP client.

When this launches, it will ask you for the tunnel username. This will be "tunnel" that you configured above. You can also hard code this if you make a copy of this jnlp file so the user doesn't need to enter in this information ever time. Add in these two lines to the properties:

<property name="crushtunnel.remote.user" value="tunnel"/> <property name="crushtunnel.remote.pass" value="tunnel"/>


Once the tunnel has been started, you can use any FTP client on the same machine, and go to:


Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
advanced_upload.png 25.7 kB 2 09-Oct-2016 18:14 Ben Spink
crushtunnel_diagram.png 80.7 kB 1 09-Oct-2016 18:14 Ben Spink
download_basket.png 39.9 kB 1 09-Oct-2016 18:14 Ben Spink
jnlp.png 25.7 kB 1 09-Oct-2016 18:14 Ben Spink
ports.png 50.1 kB 2 09-Oct-2016 18:14 Ben Spink
prefs_tunnel.png 77.9 kB 3 09-Oct-2016 18:14 Ben Spink
tunnel_only.png 74.7 kB 1 09-Oct-2016 18:14 Ben Spink
user_tunnel.png 22.0 kB 2 09-Oct-2016 18:14 Ben Spink
user_tunnel_client.png 268.4 kB 2 09-Oct-2016 18:14 Halmágyi Árpád
« This particular version was published on 09-Oct-2016 18:14 by Ben Spink.
G’day (anonymous guest)


New: CrushFTPv9#


CrushFTP8 | What's New
JSPWiki v2.8.2