Pagekite revisited

Pagekite – The fast, reliable localhost tunneling solution

PageKite makes local websites or SSH servers publicly accessible in mere seconds, and works with any computer and any Internet connection.

——————————————————————————————————————-
27th December 2010
——————————————————————————————————————–
Whether it’s a personal blog, photos of your kids, or a brand new web-app you’ve built from scratch, pageKite lets you run websites on your own computers – no hosting required!

This page should contain information on how to use the Python implementation of the pageKite tunneling protocol, pagekite.py.

What it does

The pagekite.py program does quite a few things, all of which serve the purpose of making your website visible to the wider Internet:

It creates a tunnel between your web server and the pageKite front-end servers.
It automatically chooses the front-end(s) closest to you.
It updates the DNS records for your domains whenever your front-ends change.
What it doesn’t do (yet)

It doesn’t restrict or alter traffic in any way (censorship, access control, virus protection, …)
It isn’t a web server (a basic one is built in, but it’s just for viewing the current state)
How to run it

Given the following assumptions:

You have Python 2.2 or newer installed on your computer
You have the domain you.pagekite.me
Your shared secret is ABCD
Run the program like this:

./pagekite.py –defaults \
–backend=http:you.pagekite.me:localhost:9999:ABCD
It should write some logging messages to the console, hopefully registering the domain and a tunnel to pageKite.net. Watch out for the word “rejected” – if you see that, then it probably means you got the domain name or shared secret wrong.

Once pagekite.py is up and running, point your web browser at localhost:9999, to see the current state of the program. Hopefully it will list at least one “flying kite” and clicking a link will take you to the same page on the public Internet: you.pagekite.me

This is pagekite.py serving up it’s internal status page as your public website. Not the most interesting use case!

Next let’s assume you have a web server running on ports 8080 and 8443 (the latter serving up encrypted HTTPS pages).

Run pagekite.py like so:

pagekite.py –defaults \
–backend=http:you.pagekite.me:localhost:8080:ABCD \
–backend=https:you.pagekite.me:localhost:8443:ABCD
This should make your web server publicly visible on the Internet (on the standard ports, 80 and 443), both for encrypted and regular HTTP traffic! Mission accomplished!

To “land the kite”, just hit CTRL+C in the console window at any time.

http://pagekite.net/

Also see:-
http://www.unhosted.org/

and unite, built into the Opera web browser

Note:-
Most Linux distributions have LAMP (Linux/Apache/Mysql/Php) available.
Put your content where the server can  find it, usually /var/www/
Then type http://localhost in your browser to see your website. Once it works, open port 80 on your router and you will be able to see your site from anywhere, using the IP address of your router.
If you want to access it by name instead of IP, sign up for a free account at DynDNS.
If you want more than static pages, try installing Drupal,Joomla or WordPress.

Advertisements

2 thoughts on “Pagekite revisited

  1. Hey, thanks for mentioning PageKite!

    Your entry is a bit of an odd copy-paste of some of the instructions I wrote a few months back. That is fine, most if it is still valid, but you are missing one key thing, which is that these instructions all assume the user has already signed up for an account with http://pagekite.net/.

    Although you can run pagekite.py on your own (it is FOSS after all), these instructions only work if you've signed up for the service.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s