is tool using reverse proxy to create a tunnel to your localhost which is then publicly accessible from outside your networks, and this is also known as localhost tunneling which is especially useful when you want to quickly test or access a local running web app behind NAT and firewall from outside of your networks and don’t want to go through the complicated processes such as: buying a cloud-based server like vps for dns configuration with public static ip, or deployment to cloud based instances like aws ec2, and etc.


  • Pagekite backend: A pagekite backend is your local running web app that is behind NAT or firewall and does not have publicly accessible static ip address and domain name. It is the one you want to be exposed to internet.
  • Pagekite frontend: A pagekite frontend is a proxy server that is on the internet with a publicly accessible static ip address or domain name and to which a pagekite backend is connecting to for proxy and also through which outsiders can access for further accessing your local running web app.

How to install

  • Install for backend (Mac, Linux)
$ curl -s |sudo bash

# After above command succeeds, should be available at:

# See help doc
$ --help
  • Install for frontend (Linux - Ubuntu)
# Add our repository to /etc/apt/sources.list
$ echo deb pagekite main | sudo tee -a /etc/apt/sources.list

# Add the PageKite packaging key to your key-ring
$ sudo apt-key adv --recv-keys --keyserver AED248B1C7B2CAC3

# Refresh your package sources by issuing
$ sudo apt-get update

# Install pagekite !
$ sudo apt-get install pagekite

# After above steps, pagekite command should be available at:

Note that installing with deb (apt) or rpm (yum) will install bonus scripts for auto start and upgrade and configs, so it should be preferred on linux (ubuntu or centos).

How to config frontend

# Remove all lines in below file:
sudo vi /etc/pagekite.d/10_account.rc

# Edit below file:
sudo vi /etc/pagekite.d/20_frontend.rc
# Add below content:
# ports that frontend is listening for local service to connect to and also for outsiders to access, comma separated, such as 80,443
# protocols that frontend is using for outsiders to access, such as http,https
# domain of the frontend server and password is for backend authentication during pagekite connection
# if dns is configured to allow for wildcard naming resolution, then using the * like below gives users free choices for kite names
# if tls/ssl will be used (e.g. 443 port), then below entry is for specifying the pem file (containing certificate and key)

How to config backend with rc file and make connection to expose local services

  • Create a config file at: ~/.pagekite.rc with below content
  • Run command below to expose http://localhost:8080 for example:
  • Run command below to expose running web app on other known hosts (with ip: x.x.x.x):
$ x.x.x.x:yy KITENAME
  • Run command below to expose a local directory and files:
$ <directory> KITENAME +indexes
  • Run command below to expose html files:
$ *.html KITENAME
  • NOTE: If need different KITENAMEs for above examples, multiple kitename entries should be added in ~/.pagekite.rc file:

How to connect to frontend directly from command line without using ~/.pagekite.rc

# expose a local service running on port 8080
## specify proto and port:
$ --clean --frontend=FRONTEND-HOST:FRONTEND-PORT --service_on=http/8080:KITENAME:localhost:8080:password
## specify proto and use default port frontend is listening on
$ --clean --frontend=FRONTEND-HOST:FRONTEND-PORT --service_on=http:KITENAME:localhost:8080:password


  • can not only be used for exposing http service, but also ssh or technically any other protocols
  • can also be used to quickly expose static files or directories thanks to its built web http server
  • is a paid frontend where you can register a custom name like for public access
  • Similar tools and services are also available, such as: ngrok, localtunnel, and etc.
  • Pagekite is open source and available here


Post tagged with: networking