Can’t (or don’t want to) make Instiki run on port 80, but can’t access anything else externally? One option—an excellent option, actually—is to use SSH port forwarding. Here are the steps:
http://your-site.com:2500) and observe that you can’t1.
ssh -L 2500:your-site.com:2500 -l yourname -N your-site.com
http://localhost:2500. It should work this time.
localhost:2500and transmits to the server over port 22.
your-site.com:2500which it can do because it’s on the same machine.
You’ve tunneled through the firewall by using an allowed port to access a disallowed port. The mechanism was SSH. That’s why this technique is commonly called SSH tunneling.
All SSH traffic is strongly encrypted, so that’s an extra benefit of this solution.
I also have a Fire Fox? keyword set (
swikis, for “secure wikis”) so I can access them in a flash.
Jamis Buck’s excellent net-ssh package enables you to perform SSH operations, including port forwarding, with Ruby. I’m trying to create a program that does the tunneling for me, and which is installed as an always-on service, so my Wiki is always accessible and I don’t have to run Pu TTY?. If anyone has written a program like this, please let me know.
This tutorial was written by Gavin Sinclair and I am the first to ackknowledge that it could be improved. If you want to access your Wiki using this method and are having trouble, email me and I’ll help you out and improve this page.
1 If you can access it, then stop reading this tutorial, unless you want to use SSH for security.
ssh knowledge is assumed here.