Websites with the Cherokee Web Server on Debian 5 (Lenny)

Select distribution:
Traducciones al Español
Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Deprecated

This guide has been deprecated and is no longer being maintained.

Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

Cherokee is a fast, flexible web server for POSIX compliant operating systems such as Linux. It’s designed to be easy to administer, and includes support for a wide range of common web server functions.

This tutorial explains how to install and configure the Cherokee web server on Debian 5 (Lenny). This guide targets Cherokee version 0.7.2 (provided by the Debian repositories as of this writing), but the install steps should be similar for later versions. We will be performing the installation through the terminal; please make sure you are logged into your Linode as root via SSH.

This document assumes that you already have a working and up to date Debian 5 (Lenny) system. If you have not followed our Setting Up and Securing a Compute Instance, we recommend that you do so prior to following these instructions.

Install Cherokee

Make sure your package repositories and installed programs are up to date by issuing the following commands:

apt-get update
apt-get upgrade --show-upgraded

Enter the following command to install the Cherokee web server, its documentation and a collection of utilities.

apt-get install cherokee

Several packages will be installed in addition to the main server package. You may visit your Linode’s IP address (or domain name, if you have it pointed to the IP) in a web browser to verify that Cherokee is running. You should see the default Cherokee test page.

If you need support for SSL sites, issue the following command to install OpenSSL:

apt-get install openssl

Configuring Cherokee

The Cherokee web server includes an easy to use, comprehensive administration interface. This interface, known as cherokee-admin, is the recommended means of administering your web server.

Start cherokee-admin by issuing the following command:

cherokee-admin -b &

This instructs the administration program to bind to all IP addresses so it may be reached remotely. It will be launched in the background, so you’ll still be able to use your SSH session. You should see output similar to the following:

archimedes:~# cherokee-admin -b &
[1] 2976
archimedes:~# Cherokee Web Server 0.7.2 (Sep  1 2008): Listening on port 9090, TLS disabled
 IPv6 disabled, using epoll, 1024 fds system limit, max. 507 connections
 20 threads, 54 fds per thread, standard scheduling policy

Secure Admin Panel Access

Please note that in version 0.7.2, a login is not required to access cherokee-admin (although in the current version a one-time password is used). This is due to the default behavior of binding only to 127.0.0.1 (localhost). Instead of binding to all interfaces on your Linode, you may wish to bind to localhost and use SSH port forwarding to securely reach the administration system from your workstation. To do so, issue the following commands to launch cherokee-admin and set up an SSH tunnel. The first command is not required if you haven’t already launched cherokee-admin. You may need to install the killall command first by issuing apt-get install psmisc on your Linode.

On your Linode:

killall cherokee-admin
cherokee-admin &

In a terminal window on your local workstation (MacOS X, Linux, BSD, etc) :

ssh -L 9090:localhost:9090 root@12.34.56.78 -N

Replace “12.34.56.78” with your Linode’s IP address. You may now visit http://localhost:9090 in your web browser via the SSH tunnel. To stop the tunnel, simply press Ctrl+C in your local terminal window.

You’ll be presented with the Cherokee administration panel, which you may use to configure websites and specify configuration options.

Secure Admin Panel Access on Windows

You can use PuTTY to set up a secure SSH tunnel for Cherokee administration. Enter your Linode’s public IP address in the session tab:

Session information for PuTTY.

Expand the “Connection -> SSH” menus to select the “Tunnel” configuration page. Enter the values shown here:

Configuring an SSH tunnel for Cherokee administration in PuTTY.

Back on the session tab, enter “Cherokee Admin” in the “Saved Sessions” field and click “Save” to retain your settings for future use.

Saving an SSH session for Cherokee administration in PuTTY.

Click “Open” to connect to your server and start the tunnel. You may receive a warning similar to the one shown here:

An SSH key alert in PuTTY.

Click “Yes” to continue, and log into your Linode as you normally would. As long as the SSH session is open you’ll be able to navigate to http://localhost:9090 in your web browser to access the Cherokee admin panel via the secure tunnel.

Conclusion

Be sure to stop cherokee-admin using the killall command shown above once you’re done configuring your system. Congratulations, you’ve successfully installed the Cherokee web server on your Linode!

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

This page was originally published on


Your Feedback Is Important

Let us know if this guide was helpful to you.


Join the conversation.
Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our Support team or asking on our Community Site.
The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please update your Cookie Preferences on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.