Tag Archives: lighttpd

geek howto

HOWTO: log the user's IP, not the proxy's, in nginx access log

December 18, 2008 – 12:55 pm
nginx

nginx

So back in January I had a post about HOWTO: log the user’s IP, not the proxy’s, in Lighttpd access log, but today I switched that system to run nginx (actually nginx has been running since early this year, I just got lazy on running Varnish) fronted again by Varnish. I had the same issue, but not much trouble solving it. Since I often refer to my own notes on fak3r, I’m recording it here for myself, and anyone streaming in from Google. So, as I talked about before, when you run a webserver behind Varnish doing http acceleration, the webserver access logs will display the IP of the proxy (generally 127.0.0.1) instead of the end user’s IP. This not only breaks any kind of tracking or reporting you want to run against your webserver logs. Since this server runs Varnish in front of nginx, and it reveals the end user’s IP in the header as X-Forwarded-For, so it’s just a matter of making nginx use that variable in its access logs instead of the default variable defining the referring IP. Once we know that, the configuration is simple.  Edit your nginx.conf file:

This is a preview of HOWTO: log the user's IP, not the proxy's, in nginx access log. Read the full post (252 words, 1 image, estimated 1:00 mins reading time)
Tags , , , , | Permalink | Comments (7)
geek linux

HOWTO: Configure nginx for Debian / Ubuntu

May 5, 2008 – 12:20 pm

nginxUPDATE: I’m reworking my config blending in the security ideas found on camomel.org they’re really thought things through on this, this should make for a very secure environment.

This is a preview of HOWTO: Configure nginx for Debian / Ubuntu. Read the full post (350 words, 1 image, estimated 1:24 mins reading time)
Tags , , , , , | Permalink | Comments (12)
geek howto

HOWTO: determine optimal fastcgi settings for Lighttpd

February 28, 2008 – 11:50 am

PHP Fast-cgiAnyone building a server with a LAMP stack today has tons of options, mine have evolved to using Varnish -> Lighttpd -> Xcache -> PHP5 -> MySQL. Once I had Lighttpd (aka Lighty) installed and running PHP pages I looked to optimize the configuration and push it as hard as possible for more speed. Of course lately I’ve been getting unexplained slowdowns, with many instances of php5-cgi appearing to be taking up almost all of my available CPU on `top`. Reading up on things it appears that I had max_procs, along with PHP_FCGI_CHILDREN, set far too high for the load I’m getting. When you start lighty it gives you the number of processes you’ve define, and then those in turn spawn the number of children you’ve specified. While my settings were too high, they were really overshooting things when you take into account that I’m using Xcache (which provides PHP pre-caching) and Varnish (for HTTP acceleration). So even though one of my dynamic sites that I’m working on to ‘monetize’ things is getting 700-800 hits each day, my caching strategy is taking the load away from the ever available Lighty. Because of this, lighty has much less to do, so giving it a ton of processes to just sit there and eat memory until they’re zombified is a waste. After reading the lighty FAQ and other posts specific to this, I’ve settled on the this for my fastcgi config block within my lighttpd.conf file.

This is a preview of HOWTO: determine optimal fastcgi settings for Lighttpd. Read the full post (325 words, 1 image, estimated 1:18 mins reading time)
Tags , , , , , , , , | Permalink | Comment (0)
geek howto

HOWTO: use monit to keep Lighttpd and Varnish running

February 19, 2008 – 1:51 pm

IgnignoktThanks to a post from Steve over at debian-administration.org, I finally got around to setting up monit, the little monitoring app we use at work to keep things sane.  I was getting around to installing it at home, but it became more urgent when Varnish went down last week; without it running there’s nothing to handle requests on :80, so as a webserver it’s dead. So here’s my monitrc for the webserver Lighttpd fronted by Varnish, acting in the reverse proxy/http accel role. Varn is listening on 80, then, if things aren’t cached, it forwards things on to Lighttpd listening on 82. Lighty also listens on the standard 443 for HTTPS requests, so we check that as well.

This is a preview of HOWTO: use monit to keep Lighttpd and Varnish running. Read the full post (350 words, 1 image, estimated 1:24 mins reading time)
Tags , , , , | Permalink | Comments (10)
geek howto linux

HOWTO: log the user's IP, not the proxy's, in Lighttpd access log

January 9, 2008 – 10:17 am

Lighttpd - fly lightWhen you run a webserver behind a reverse proxy or HTTP accelerator like Squid or Varnish, the webserver access logs will display the IP of the proxy (generally 127.0.0.1) instead of the end user’s IP.  This not only breaks any kind of tracking or reporting you want to run against your webserver logs, but it also takes away a datapoint I’ve had use for in general server admin tasks. This server runs Varnish in front of Lighttpd, and it reveals the end user’s IP in the header as X-Forwarded-For, so it’s just a matter of making Lighttpd (lighty) use that variable in its access logs instead of the default variable defining the referring IP. Once we know that, the configuration is simple; in lighttpd.conf, enter this:

This is a preview of HOWTO: log the user's IP, not the proxy's, in Lighttpd access log. Read the full post (182 words, 1 image, estimated 44 secs reading time)
Tags , , , , , , , , , , | Permalink | Comments (11)