Introducing API calls

5 years ago

Automate your tasks with API calls

Good news everyone! As of today supports API calls. You can now open and close tunnels without visiting the website and clicking on/off button but by simply issuing an API call using your any scripting language. For instance, you can open a tunnel using bash script with the command like:

result=$(curl '' | jq -r '.success')

or if you prefer python it would look something like:

api_endpoint = '{0}?dbid=Bad9alsdS920a11-Aqj2&host_uuid=20sldd20-20sz-aa20-aa02-aa0salskd82a&ports_id=1234&user_id=12345'
# open the tunnel
json_result = json.loads(urllib2.urlopen(api_endpoint.format('connect')).read())

This can help in automating your administrative tasks and in maintaining your servers. For detailed documentation check here.


Introducing Windows support

5 years ago

We are proud to announce that as of today we officially support running client scripts on Windows operating systems.

Although was first conceived as a primarily Linux and Mac oriented service, we have recognized the need to support Windows systems. So, if you are a web developer working on Windows and you want to show your work in progress to your prospective client on your computer, you can now do it with You can also use to test your application's webhooks during development process. Or if you need to provide remote support to your client, you can install and VNC server on your client's PC and have on-demand encrypted VNC connection with them.

Unfortunately, Windows operating systems do not support ssh and python scripts out-of-the-box, so there are a few additional steps to take before you can open a tunnel from your Windows machine. If you would like to run client on Windows, we’ve created a detailed step-by-step manual here.


Introducing regional forwarding servers

6 years ago

If you are one of our users and your servers were not in Europe, we know that using has probably not always been a smooth experience. Reaching your computer through our forwarding server has sometimes been too slow and laggy. The reason for this was geographical distance between our forwarding servers and your computer, as all our servers were based in Europe.

As of today this is going to change because we're introducing support for regional forwarding servers. This means that for every new client you will get to choose a region.

Once you've chosen your region, your forwarding connection will always be open on it, resulting in much faster response time and a better user experience.



Using to test your webhooks

6 years ago

One of the often overlooked but very useful features of is the ability to use it to develop and test webhooks in your web app while it is still on your dev computer and behind a firewall. Let me show you how, using an example.

Suppose you develop a web application and in your web app you want to use PayPal’s services to allow your customers to buy your goods or services. During development you will, of course, use PayPal’s sandbox site where you can simulate and test the process of transferring funds from your customers to you. One of the mechanisms through which PayPal informs you of the money transfer is web notifications (in PayPal’s case they can be called webhooks or IPN or PDT API-s, but the process is similar). Simply said, web notifications or webhooks are special URLs in your web app, through which PayPal informs you of any changes in your account.

Testing those webhooks can present a challenge since your development computer is probably behind a firewall. If you have a static IP, you could probably set up port forwarding on your firewall, but it would mean that your dev environment is constantly open to the world; or, if you do not have a static IP, you would probably need to set up a sandbox server which has to be publicly accessible, and then transfer your dev environment to that server and then push changes from your computer to the testing server every time you make changes to the webhook code. This can become annoying very quickly.

With, you can just tunnel your development web server’s port through the’s tunnel and then set the PayPal’s notification URLs to the appropriate tunnel exit point. Furthermore, you can open and close the tunnel whenever you need to, so your development server is not visible on the whole internet all the time.

First, just create a new client and forward port number 80 (or whatever your dev server is listening to).



Once the client is created, you can find the entry point on the Info tab (for example:

All you need to do now is set up your PayPal’s notification URLs using the above info. For instance, to set up your PDT listener URL, like in this example:

And to set up your IPN listener URL:

Once these settings are saved, you can just open the tunnel and begin testing. When you are sure everything works properly, just close the tunnel and that’s it. Happy coding!



We now support forwarding any port

7 years ago now allows you to forward any port from your computer or server. So for instance, if you are a web developer who would like to share its work with its client you can now forward port 80 from your computer and thus allow your customer to see your work in development on your computer. When you create a new client all you have to do is to fill the value for the port to be forwarded.

Furthermore, we have added another layer of security. If you check the "source ip protection" checkbox, access to the forwarded client will be accessible only to the one client who you've given access to. To give access to your customer all you have to do is to send them a link that appears in the "Open firewall for IP" column.

When the customer opens the link they will see the following text and they will be granted access to your port forwarded computer.


This access only lasts until the tunnel is closed.

Older entries... Newer entries...