Performance Calendar

user www-data;
worker_processes 2;
pid /var/run/nginx.pid;
 
events {
    worker_connections 768;
    multi_accept on;
    use epoll;
}
 
http {
 
    # Let NGINX get the real client IP for its access logs
    set_real_ip_from 127.0.0.1;
    real_ip_header X-Forwarded-For;
 
    # Basic Settings
    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 20;
    client_max_body_size 15m;
    client_body_timeout 60;
    client_header_timeout 60;
    client_body_buffer_size  1K;
    client_header_buffer_size 1k;
    large_client_header_buffers 4 8k;
    send_timeout 60;
    reset_timedout_connection on;
    types_hash_max_size 2048;
    server_tokens off;
 
    # server_names_hash_bucket_size 64;
    # server_name_in_redirect off;
 
    include /etc/nginx/mime.types;
    default_type application/octet-stream;
 
    # Logging Settings
    # access_log /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log;
 
    # Log Format
    log_format main '$remote_addr - $remote_user [$time_local] '
    '"$request" $status $body_bytes_sent "$http_referer" '
    '"$http_user_agent" "$http_x_forwarded_for"';
 
    # Gzip Settings
    gzip on;
    gzip_static on;
    gzip_disable "msie6";
    gzip_vary on;
    gzip_proxied any;
    gzip_comp_level 6;
    gzip_min_length 512;
    gzip_buffers 16 8k;
    gzip_http_version 1.1;
    gzip_types text/css text/javascript text/xml text/plain text/x-component 
    application/javascript application/x-javascript application/json 
    application/xml  application/rss+xml font/truetype application/x-font-ttf 
    font/opentype application/vnd.ms-fontobject image/svg+xml;
 
    # Virtual Host Configs
    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;
}

    application/vnd.ms-fontobject           eot;
    application/x-font-ttf                  ttf;
    font/opentype                           ott;
    application/font-woff                   woff;

server {
    # Default server block blacklisting all unconfigured access
    listen [::]:8080 default_server;
    server_name _;
    return 444;
}
 
server {
    # Configure the domain that will run WordPress
    server_name yourdomain.tld;
    listen [::]:8080 deferred;
    port_in_redirect off;
    server_tokens off;
    autoindex off;
 
    client_max_body_size 15m;
    client_body_buffer_size 128k;
 
    # WordPress needs to be in the webroot of /var/www/ in this case
    root /var/www;
    index index.html index.htm index.php;
    try_files $uri $uri/ /index.php?q=$uri&$args;
 
    # Define default caching of 24h
    expires 86400s;
    add_header Pragma public;
    add_header Cache-Control "max-age=86400, public, must-revalidate, proxy-revalidate";
 
    # deliver a static 404
    error_page 404 /404.html;
    location  /404.html {
        internal;
    }
 
    # Deliver 404 instead of 403 "Forbidden"
    error_page 403 = 404;
 
    # Do not allow access to files giving away your WordPress version
    location ~ /(\.|wp-config.php|readme.html|licence.txt) {
        return 404;
    }
 
    # Add trailing slash to */wp-admin requests.
    rewrite /wp-admin$ $scheme://$host$uri/ permanent;
 
    # Don't log robots.txt requests
    location = /robots.txt {
        allow all;
        log_not_found off;
        access_log off;
    }
 
    # Rewrite for versioned CSS+JS via filemtime
    location ~* ^.+\.(css|js)$ {
        rewrite ^(.+)\.(\d+)\.(css|js)$ $1.$3 last;
        expires 31536000s;
        access_log off;
        log_not_found off;
        add_header Pragma public;
        add_header Cache-Control "max-age=31536000, public";
    }
 
    # Aggressive caching for static files
    # If you alter static files often, please use 
    # add_header Cache-Control "max-age=31536000, public, must-revalidate, proxy-revalidate";
    location ~* \.(asf|asx|wax|wmv|wmx|avi|bmp|class|divx|doc|docx|eot|exe|
    gif|gz|gzip|ico|jpg|jpeg|jpe|mdb|mid|midi|mov|qt|mp3|m4a|mp4|m4v|mpeg|
    mpg|mpe|mpp|odb|odc|odf|odg|odp|ods|odt|ogg|ogv|otf|pdf|png|pot|pps|
    ppt|pptx|ra|ram|svg|svgz|swf|tar|t?gz|tif|tiff|ttf|wav|webm|wma|woff|
    wri|xla|xls|xlsx|xlt|xlw|zip)$ {
        expires 31536000s;
        access_log off;
        log_not_found off;
        add_header Pragma public;
        add_header Cache-Control "max-age=31536000, public";
    }
 
    # pass PHP scripts to Fastcgi listening on Unix socket
    # Do not process them if inside WP uploads directory
    # If using Multisite or a custom uploads directory,
    # please set the */uploads/* directory in the regex below
    location ~* (^(?!(?:(?!(php|inc)).)*/uploads/).*?(php)) {
        try_files $uri = 404;
        fastcgi_split_path_info ^(.+.php)(.*)$;
        fastcgi_pass unix:/var/run/php-fpm.socket;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
        fastcgi_intercept_errors on;
        fastcgi_ignore_client_abort off;
        fastcgi_connect_timeout 60;
        fastcgi_send_timeout 180;
        fastcgi_read_timeout 180;
        fastcgi_buffer_size 128k;
        fastcgi_buffers 4 256k;
        fastcgi_busy_buffers_size 256k;
        fastcgi_temp_file_write_size 256k;
    }
 
    # Deny access to hidden files
    location ~ /\. {
        deny all;
        access_log off;
        log_not_found off;
    }
 
}
 
# Redirect all www. queries to non-www
# Change in case your site is to be available at "www.yourdomain.tld"
server {
    listen [::]:8080;
    server_name www.yourdomain.tld;
    rewrite ^ $scheme://yourdomain.tld$request_uri? permanent;
}

short_open_tag = Off
ignore_user_abort = Off
post_max_size = 15M
upload_max_filesize = 15M
default_charset = "UTF-8"
allow_url_fopen = Off
default_socket_timeout = 30
mysql.allow_persistent = Off

[apc]
apc.stat = "0"
apc.max_file_size = "1M"
apc.localcache = "1"
apc.localcache.size = "256"
apc.shm_segments = "1"
apc.ttl = "3600"
apc.user_ttl = "7200"
apc.gc_ttl = "3600"
apc.cache_by_default = "1"
apc.filters = ""
apc.write_lock = "1"
apc.num_files_hint= "512"
apc.user_entries_hint="4096"
apc.shm_size = "256M"
apc.mmap_file_mask=/tmp/apc.XXXXXX
apc.include_once_override = "0"
apc.file_update_protection="2"
apc.canonicalize = "1"
apc.report_autofilter="0"
apc.stat_ctime="0"
;This should be used when you are finished with PHP file changes.
;As you must clear the APC cache to recompile already cached files.
;If you are still developing, set this to 1.
apc.stat="0"

pid = /var/run/php5-fpm.pid
error_log = /var/log/php5-fpm.log
emergency_restart_threshold = 5
emergency_restart_interval = 2
events.mechanism = epoll

user = www-data
group = www-data
listen = /var/run/php-fpm.socket
listen.owner = www-data
listen.group = www-data
listen.mode = 0666
listen.allowed_clients = 127.0.0.1
pm = dynamic
pm.max_children = 50
pm.start_servers = 15
pm.min_spare_servers = 5
pm.max_spare_servers = 25
pm.process_idle_timeout = 60s
request_terminate_timeout = 30
security.limit_extensions = .php

php_flag[display_errors] = off
php_admin_value[error_reporting] = 0
php_admin_value[error_log] = /var/log/php5-fpm.log
php_admin_flag[log_errors] = on
php_admin_value[memory_limit] = 128M

DAEMON_OPTS="-a :80 \
    -T localhost:6082 \
    -f /etc/varnish/default.vcl \
    -u www-data -g www-data \
    -S /etc/varnish/secret \
    -p thread_pools=2 \
    -p thread_pool_min=25 \
    -p thread_pool_max=250 \
    -p thread_pool_add_delay=2 \
    -p session_linger=50 \
    -p sess_workspace=262144 \
    -p cli_timeout=40 \
    -s malloc,768m"

# We only have one backend to define: NGINX
backend default {
    .host = "127.0.0.1";
    .port = "8080";
}
 
# Only allow purging from specific IPs      
acl purge {
    "localhost";
    "127.0.0.1";
}
 
sub vcl_recv {
    # Handle compression correctly. Different browsers send different
    # "Accept-Encoding" headers, even though they mostly support the same
    # compression mechanisms. By consolidating compression headers into
    # a consistent format, we reduce the cache size and get more hits.
    # @see: http:// varnish.projects.linpro.no/wiki/FAQ/Compression
    if (req.http.Accept-Encoding) {
        if (req.http.Accept-Encoding ~ "gzip") {
            # If the browser supports it, we'll use gzip.
            set req.http.Accept-Encoding = "gzip";
        }
        else if (req.http.Accept-Encoding ~ "deflate") {
            # Next, try deflate if it is supported.
            set req.http.Accept-Encoding = "deflate";
        }
        else {
            # Unknown algorithm. Remove it and send unencoded.
            unset req.http.Accept-Encoding;
        }
    }
 
    # Set client IP
    if (req.http.x-forwarded-for) {
        set req.http.X-Forwarded-For =
        req.http.X-Forwarded-For + ", " + client.ip;
    } else {
        set req.http.X-Forwarded-For = client.ip;
    }
 
    # Check if we may purge (only localhost)
    if (req.request == "PURGE") {
        if (!client.ip ~ purge) {
            error 405 "Not allowed.";
        }
        return(lookup);
    }
 
    if (req.request != "GET" &&
        req.request != "HEAD" &&
        req.request != "PUT" &&
        req.request != "POST" &&
        req.request != "TRACE" &&
        req.request != "OPTIONS" &&
        req.request != "DELETE") {
            # /* Non-RFC2616 or CONNECT which is weird. */
            return (pipe);
    }
 
    if (req.request != "GET" && req.request != "HEAD") {
        # /* We only deal with GET and HEAD by default */
        return (pass);
    }
 
    # admin users always miss the cache
    if( req.url ~ "^/wp-(login|admin)" || 
        req.http.Cookie ~ "wordpress_logged_in_" ){
            return (pass);
    }
 
    # Remove cookies set by Google Analytics (pattern: '__utmABC')
    if (req.http.Cookie) {
        set req.http.Cookie = regsuball(req.http.Cookie,
            "(^|; ) *__utm.=[^;]+;? *", "\1");
        if (req.http.Cookie == "") {
            remove req.http.Cookie;
        }
    }
 
    # always pass through POST requests and those with basic auth
    if (req.http.Authorization || req.request == "POST") {
        return (pass);
    }
 
    # Do not cache these paths
    if (req.url ~ "^/wp-cron\.php$" ||
        req.url ~ "^/xmlrpc\.php$" ||
        req.url ~ "^/wp-admin/.*$" ||
        req.url ~ "^/wp-includes/.*$" ||
        req.url ~ "\?s=") {
            return (pass);
    }
 
    # Define the default grace period to serve cached content
    set req.grace = 30s;
 
    # By ignoring any other cookies, it is now ok to get a page
    unset req.http.Cookie;
    return (lookup);
}
 
sub vcl_fetch {
    # remove some headers we never want to see
    unset beresp.http.Server;
    unset beresp.http.X-Powered-By;
 
    # only allow cookies to be set if we're in admin area
    if( beresp.http.Set-Cookie && req.url !~ "^/wp-(login|admin)" ){
        unset beresp.http.Set-Cookie;
    }
 
    # don't cache response to posted requests or those with basic auth
    if ( req.request == "POST" || req.http.Authorization ) {
        return (hit_for_pass);
    }
 
    # don't cache search results
    if( req.url ~ "\?s=" ){
        return (hit_for_pass);
    }
 
    # only cache status ok
    if ( beresp.status != 200 ) {
        return (hit_for_pass);
    }
 
    # If our backend returns 5xx status this will reset the grace time
    # set in vcl_recv so that cached content will be served and 
    # the unhealthy backend will not be hammered by requests
    if (beresp.status == 500) {
        set beresp.grace = 60s;
        return (restart);
    }
 
    # GZip the cached content if possible
    if (beresp.http.content-type ~ "text") {
        set beresp.do_gzip = true;
    }
 
    # if nothing abovce matched it is now ok to cache the response
    set beresp.ttl = 24h;
    return (deliver);
}
 
sub vcl_deliver {
    # remove some headers added by varnish
    unset resp.http.Via;
    unset resp.http.X-Varnish;
}
 
sub vcl_hit {
    # Set up invalidation of the cache so purging gets done properly
    if (req.request == "PURGE") {
        purge;
        error 200 "Purged.";
    }
    return (deliver);
}
 
sub vcl_miss {
    # Set up invalidation of the cache so purging gets done properly
    if (req.request == "PURGE") {
        purge;
        error 200 "Purged.";
    }
    return (fetch);
}
 
sub vcl_error {
    if (obj.status == 503) {
                # set obj.http.location = req.http.Location;
                set obj.status = 404;
        set obj.response = "Not Found";
                return (deliver);
    }
}

Varnish Administration IP Address: 127.0.0.1
Varnish Administration Port: 80
Varnish Secret: (get it at /etc/varnish/secret)
Check: "Also purge all page navigation" and "Also purge all comment navigation"
Varnish Version: 3

/**
 * Automated cache-buster function via filemtime
 **/
function autoVer($url){
  $name = explode('.', $url);
  $lastext = array_pop($name);
  array_push(
    $name, 
    filemtime($_SERVER['DOCUMENT_ROOT'] . parse_url($url, PHP_URL_PATH)), 
    $lastext);
  echo implode('.', $name) ;
}

# Add in your theme's functions.php:
wp_register_style(
  'style', 
  get_bloginfo('stylesheet_directory') . autoVer('style.css'), 
  false, 
  NULL, 
  'all');
 
# Add in your theme's header.php:
autoVer(get_bloginfo('stylesheet_url'))

<?php
    /*
     * Circumvent @import CSS for WordPress child themes
     * If we're in a child theme, build links for both parent and child CSS
     * This way, we can remove the @import from the child theme's style.css
     * CSS loaded via link can load simultaneously, while @import blocks loading
     * See: http://www.stevesouders.com/blog/2009/04/09/dont-use-import/
     */
    if(is_child_theme()) {
        echo '<link rel="stylesheet" href="';
        autoVer(get_bloginfo('template_url').'/style.css');
        echo '" />'."\n\t\t";
        echo '<link rel="stylesheet" href="';
        autoVer(get_bloginfo('stylesheet_url'));
        echo '" />'."\n";
    } else {
        echo '<link rel="stylesheet" href="';
        autoVer(get_bloginfo('stylesheet_url'));
        echo '" />'."\n";
    } 
?>

51 Responses to “Using NGINX, PHP-FPM+APC and Varnish to make WordPress Websites fly”

1. Die Adventskalender am 7. Dezember « F-LOG-GE December 7th, 2012

   [...] verweist auf einen Link, der vor allem für JavaScript-Profis interessant sein dürfte. Beim Performancekalender gab es gestern einen Artikel über Optimierungen für [...]
2. Joseph Scott December 7th, 2012

   I’m curious, does Varnish perform significantly faster than Nginx at serving cached or static content? If the files are cached to disk (or are static) then the operating system will be caching them as well.

   
3. Pothi Kalimuthu December 8th, 2012

   Thanks for the great article, Tobias!

   @Joseph For static content, here is a direct quote from Per Buer, CEO of Varnish Software….

   Varnish is a really crappy file server and probably won’t become a very good one. And Nginx is really, really good at picking up files from the file system and serving them.

   For cached content that is stored in memory, I haven’t tested on what works best.

   When some clients insist on using WP Super Cache or W3 Total Cache for some reason, I’d go with disk based cache and let it served via Nginx.

   Personally, I prefer Nginx/php-fpm => Varnish => Nginx/php-fpm stack where Nginx listens on port 80 serving static files, Varnish caches (only) the dynamic content, and all the WP backend operations are done by Nginx/php-fpm without going through Varnish.

   
4. Today’s Readings | Aaron T. Grogg December 8th, 2012

   [...] been there so long, I just hate the idea of moving…)? Well I’ve come across two articles that caught my attention, now I just need the time and energy to try [...]
5. WordPress: die CSS-Datei des Child-Themes performance-freundlicher einbinden | WordPress & Webwork December 8th, 2012

   [...] habe ich das Code-Beispiel auf dieser Website auf die ich wiederum durch den Artikel von Jens aufmerksam geworden [...]
6. Using NGINX, PHP-FPM+APC and Varnish to make WordPress Websites fly | VietHiP December 8th, 2012

   [...] (via calendar.perfplanet.com) Share this:TwitterFacebookLike this:LikeBe the first to like this. December 8, 2012 by VietHiP Categories: Nginx, Web server | Leave a comment [...]
7. Ben Word December 10th, 2012

   Great article! Instead of editing your header template for the child theme stylesheet, you could use conditionals within a function that hooks into wp_enqueue_scripts. Here’s an example from Roots Theme:

   https://github.com/retlehs/roots/blob/master/lib/scripts.php#L23

   
8. editor December 11th, 2012

   Thanks, Ben! People had already told me to use wp_enqueue & I thought about how to change my code to reflect this. Great to see that your Roots theme has implemented this already!

   
9. Thomas December 11th, 2012

   Glimpsed over the article and looks quite good at first sight, will re-read it later when i have more time.

   One question though: Do those nginx optimisations help with other software as well like Typo3 or Magento installations?

   
10. Tobias December 12th, 2012

    @Thomas: The config for /etc/nginx/nginx.conf is quite independent of CMS etc.

    The stuff at /etc/nginx/sites-available/yourdomain.tld is partially WordPress-specific: the 404, the location blocks for readme.html etc., the directory settings, the exclusion of the uploads-directory for PHP execution etc. … You will have to go through these and change them to suit your setup. I’m sure there a plenty of good guides for Typo3 on NGINX out there.

    Remember that you’ll also need to change the config for Varnish as well as make Typo3 able to work with APC and purge the caches, esp. of Varnish.

    
11. Jozef December 13th, 2012

    Great post and instructions, really appreciated, thanks! You might want to replace all & with only & to make it direct copy paste.

    
12. Jozef December 13th, 2012

    & amp ;

    
13. The WordPress Weekend Roundup - WP Daily December 15th, 2012

    [...] 2. Optimizing NGINX, PHP-FPM+APC and Varnish [...]
14. Darren December 18th, 2012

    Great article! I’ve started working with WP/Nginx quite a bit lately, so this is all very interesting to me. I looked closely at your example server{} config, and I noticed a couple of items that either appear to be bugs, or I just don’t understand them. So I’ll mention them here in my best “constructive criticism” voice, and maybe you could clarify whether these directives were intentional (and purposeful) or simply an oversight.

    For example, I don’t understand why this is necessary:

    
# Add trailing slash to */wp-admin requests.
rewrite /wp-admin$ $scheme://$host$uri/ permanent;


    I don’t have that directive in my config, but I haven’t had any issues. Seems to me that requests for /wp-admin would already be caught by this:

    
try_files $uri $uri/ /index.php?q=$uri&$args;


    Is this redundant, or am I missing something?

    I was also wondering about this part:

    
# deliver a static 404
error_page 404 /404.html;
location /404.html {
internal;
}

    # Deliver 404 instead of 403 "Forbidden"
error_page 403 = 404;


    First, does this imply that we should create a static 404 page and save it in the web root? And if so, why doesn’t WordPress generate an error page (like it does on a standard Apache setup)?

    Second, what is the reasoning behind error_page 403 = 404?

    I haven’t seen this syntax before, so I tried this in my configuration, and the result was that the request (for a forbidden URL) was 302 redirected to /404, which doesn’t exist, so I got a 404.

    Shouldn’t it be one of these?

    # Return 404 status and serve 404.html error page
    error_page 403 =404 /404.html

    # Return 403 status and serve 404.html error page
    error_page 403 /404.html

    If your intent is simply to reuse the static 404.html error page for both types of errors (i.e., my second example above), then that makes sense. But if your intention is to actually alter the status code (i.e., your article’s version or my first example above), then what is the reasoning?

    One last thing I’ll mention…

    I’m guessing the following should say license.txt:

    
# Do not allow access to files giving away your WordPress version
location ~ /(\.|wp-config.php|readme.html|licence.txt) {
return 404;
}


    Cheers.
    -Darren

    
15. Jason McCreary December 18th, 2012

    The article would benefit from a diagram. Something to help visualize the flow from Varnish -> nginx -> PHP on various requests. Otherwise, great tutorial.

    
16. Per Buer December 20th, 2012

    Hi.

    @Joseph Scott:

    Varnish can potentially serve content faster than Nginx because it has stored it in memory and it would not require any syscalls to access that content.

    However, the difference (if any) would be minuscule and not notable. As you point out the Linux page cache would make sure that the content is kept in memory and then the cost of a couple of syscalls won’t do much.

    Nginx is blistering fast and a well written product (I’m a big fan) and we (Varnish Software) don’t recommend people setting up Varnish in front of it when only serving static content.

    
17. David Barkley January 15th, 2013

    My bird dogs sent me a couple of properties in Oklahoma and Memphis.  I must have occasion to evaluate them tomorrow.  It’s first-class to have friends!

    
18. Hakan Altun January 19th, 2013

    Hi,
    thanks for clear explanation,

    Is the second step intended for a single WP site on a host, or am I supposed to do it for each WP site on a single host?

    
19. Performance Calendar » Using NGINX, PHP-FPM+APC and Varnish to make WordPress Websites fly | Links di Davide Salerno January 25th, 2013

    [...] Performance Calendar » Using NGINX, PHP-FPM+APC and Varnish to make WordPress Websites fly. [...]
20. Mikkie January 27th, 2013

    Was this intended for Varnish 2.x or 3.x? Because that vcl config is spitting out tons of errors on Varnish 3

    
21. Mikkie January 27th, 2013

    Also, i doubt the port was set correctly here

    Varnish Administration IP Address: 127.0.0.1
    Varnish Administration Port: 80

    
22. JR January 28th, 2013

    You need to replace the ampersand html code with actual ampersands (two of them).

    It should be && instead of the text that is written.

    You should probably do the correction.

    
23. Dan Grossman January 30th, 2013

    I would highly recommend connecting to the PHP-FPM pool over TCP rather than a socket. You might lose 1-2% of potential throughput, but past a few hundred connections a second, the socket is going to start dropping connections left and right… I’m talking 10-20% of requests getting a bad gateway error with nginx reporting “resource unavailable” on the socket. Alternatively, you’d have to make multiple pools listening on different sockets and have nginx load balance across them. That’s been my experience so far.

    
24. Lee February 1st, 2013

    awesome post.. i have an old machine in the back i want to experiment with now.
    The Accept-Encoding ~ “gzip” is built into the code there, its good for speed and seo!

    
25. Pierre-Jean February 21st, 2013

    Nice article ! I was particulary interested by autoVer function, but unfortunatly I didn’t manage to make it work. I just have “style..css” appearing

    
26. Hello World! | zach.mn February 21st, 2013

    [...] I am still learning about all of the different caching options and whatnot, but I recently found this article on optimizing WordPress to the max using nginx/php-fpm+apc and Varnish.  I haven’t gone so [...]
27. Apple February 28th, 2013

    Excellent tutorial. Cheers.

    
28. Installazione Nginx – Php-fpm – Apc – Varnish e ottimizzazione wordpress su Debian 6 | iSayR March 2nd, 2013

    [...] Link [...]
29. MrFurious March 13th, 2013

    For Pierre-Jean and any others who have trouble with the autoVer function, I got it to work by replacing $_SERVER['DOCUMENT_ROOT'] with get_template_directory() and using return in the last line instead of echo (if you use the wp_register_style variant in your theme’s functions.php). All good stuff here! Thanks and cheers.

    
30. Scalability comparison of Wordpress with NGINX/PHP-FCM and Apache on an ec2-micro instance.Adventures in HttpContext | Adventures in HttpContext March 17th, 2013

    [...] straightforward nginx/php guide on Tod Sul. I also relied on an nginx tuning guide from Dakini and this nginx/wordpress tuning guide from perfplanet. They both have excellent [...]
31. Kendrick March 18th, 2013

    But it’s always wise to check in with a doctor before you start using a supplement regularly. Skiing and snowboarding are strenuous sports which demand a lot of endurance, so your usual set of ten to fifteen reps really isn”. Smoking can affect your health and fitness since it affects all the bodily functions and damages vocal cords and skin.

    Feel free to surf to my web blog: Kendrick

    
32. Paul Thomson April 1st, 2013

    Hey Tobias,

    Great post! Thanks for taking the time to write it, has helped fine tune my server quite nicely.

    I was wondering how best to go about introducing SSL to bypass Varnish? I’m got a WordPress site setup and trying to set up for secure login but I think varnish is getting in the way, ideally I would like NGINX to handle all requests on port 443.

    Any help would be greatly appreciated…

    Thanks,
    Paul

    
33. visit for golden retriever and lab mix details April 7th, 2013

    Unquestionably believe that which you said. Your
    favorite reason appeared to be on the net the easiest
    thing to be aware of. I say to you, I certainly get annoyed while people
    consider worries that they plainly do not know about. You managed to hit the nail upon the top and also defined
    out the whole thing without having side effect , people could take
    a signal. Will probably be back to get more. Thanks

    
34. foakleys frogskins April 8th, 2013

    Vous pouvez aller sur place et de choisir un accord Accessorio LV bonne aide d’un Louis Vuitton fourre-tout la seule chose dont vous faisons doit faire preuve de prudence est de vous assurer que vous ne sont pas acquérir un 1 faux. Il ya toutes sortes de fausses photos à vendre, beaucoup plus que vous trouverez les versions authentiques. foakleys frogskins http://www.pascheroakleys.net/oakley-frogskins-c-32.html

    
35. oakley gascan sunglasses April 8th, 2013

    As and Bs – Sydney Achee, Lauren Anderson, Roman Beyl, Kalie Buehler, Tyler Burdsall, Samir Cardona, Samantha Carlson, Vaughn Chase, Jessica Cobb, Alyssa Coffey, Ronnie Cooksey, Tyler Cummings, Randy Curriden, Rachael Dougherty, Kyle Durham, Dane Evans, Zachary Fox, Lacey Frey, Shannon Friant, Teresa Garrison, Alec Gruetter, Trent Hampton, Clinton Herrmann, Christopher Hill, Brooke Hyatt, Page Hyson, Kyle Kowal, Brett Lankenau, Macey Malusis, Brittany Mariano, Caitlin McCarthy, Benjamin Moyer, Gabriella Natale, Sarah Nickle, Cassie Orbin, Brianna Ottinger, James Perrone, Tayler Petrowski, Alexis Sorrels, Amanda Spinelli, Tyler Spino, Valerie Stone, Samantha Sutton, Mitchell Weiser, SaraAnn Whitzell, Nicole Williams, Sean Williamson, Francis Yangello. oakley gascan sunglasses http://www.sunglasses-soaho.org/oakley-gascan-sunglasses-p-209.html

    
36. Marc April 8th, 2013

    Hi,

    Thanks for the article, great help. However, I am getting error

    nginx: [emerg] invalid number of arguments in “location” directive in /etc/nginx/sites-enabled/example.com:70

    Is there a fix for this?

    
37. Jeromy Postert April 10th, 2013

    I as well as my friends happened to be going through the great ideas on your web blog and so quickly developed a terrible suspicion I had not thanked the web blog owner for those techniques. These young men became joyful to read through all of them and already have simply been taking pleasure in those things. Many thanks for truly being quite considerate and then for obtaining variety of essential information millions of individuals are really needing to be informed on. Our own sincere regret for not saying thanks to you earlier.

    
38. Sam April 10th, 2013

    Definitely a very helpful article. One question:

    In the sites-available configuration for nginx, you say “If using Multisite or a custom uploads directory, please set the */uploads/* directory in the regex below”

    Can you give an example of how the location directive would be different for multisite?

    Thanks!

    
39. Marv April 10th, 2013

    I have the sane Quextion as the previous one. How o adapt for multisite?

    This was a extraordinarily week written and informative post! Thank you.

    
40. Souza April 21st, 2013

    @Marc

    “”"”nginx: [emerg] invalid number of arguments in “location” directive in /etc/nginx/sites-enabled/example.com:70

    Is there a fix for this?”"”"”

    Just join the lines! Do this instead of using news lines:

    location ~* \.(asf|asx|wax|wmv|wmx|avi|bmp|class|divx|doc|docx|eot|exe|gif|gz|gzip|ico|jpg|jpeg|jpe|mdb|mid|midi|mov|qt|mp3|m4a|mp4|m4v|mpeg|mpg|mpe|mpp|odb|odc|odf|odg|odp|ods|odt|ogg|ogv|otf|pdf|png|pot|pps|ppt|pptx|ra|ram|svg|svgz|swf|tar|t?gz|tif|tiff|ttf|wav|webm|wma|woff|wri|xla|xls|xlsx|xlt|xlw|zip)$ {

    
41. Speeding up a WordPress site part 2 | Chris's blog April 26th, 2013

    [...] this combination. The one I’ve found is the best guide out there for a good start is this: Using Nginx, PHP-FPM, APC and Varnish. I a couple of small problems using that guide on a freshly installed CentOS box. I installed [...]
42. get information golden retriever stuff May 1st, 2013

    Your means of telling the whole thing in this paragraph
    is actually good, every one be able to without difficulty know it, Thanks a lot.

    
43. dating tips blog May 1st, 2013

    I love your wp web template, where did you download it through?

    Your web site does not show up correctly on my apple iphone – you might want
    to try and repair that
    Audio began playing anytime I opened up this internet site, so
    frustrating!
    I believe one of your commercials caused my browser to resize,
    you may well want to put that on your blacklist.

    I just added this website to my feed reader, excellent stuff.

    Can not get enough!
    This is a excellent web site, could you be involved in doing an interview regarding just how you developed it?

    If so e-mail me!
    Thank you, I’ve recently been seeking for info about this topic for ages and yours is the best I have discovered so far.

    
44. To Boldly Monitor What No One Has Monitored Before | tobias.is May 6th, 2013

    [...] the Performance Advent Calendar, I described how to setup a high performance webserver. As a follow-up, let’s look into monitoring this [...]
45. learn more here May 7th, 2013

    This piece of writing will assist the internet users
    for creating new webpage or even a blog from start to end.

    
46. Kontaktlinsen kaufen May 7th, 2013

    Thank you for this absolutely super article. Will now more daily . Greetings from Cologne

    
47. useful content May 7th, 2013

    Hi mates, how is the whole thing, and what you want to say concerning
    this post, in my view its really amazing designed for me.

    
48. Therese May 15th, 2013

    Your mode of explaining all in this paragraph is actually pleasant, all be able to
    effortlessly understand it, Thanks a lot.

    
49. vcl May 16th, 2013

    Error on default.vcl:

    root@s1:~# sudo /etc/init.d/varnish start
    * Starting HTTP accelerator varnishd [fail]
    Message from VCC-compiler:
    Expected ‘)’ got ‘&’
    (program line 73), at
    (‘input’ Line 52 Pos 30)

    
50. Jan Koch May 17th, 2013

    This post finally enabled me to find huge errors in my configuration!
    I head reoccurring 502 errors caused by PHP-FPM and now there gone, by adapting your configuration!

    THANK YOU SO MUCH!

    
51. Jan Koch May 17th, 2013

    This post finally enabled me to find huge errors in my configuration!
    I had reoccurring 502 errors caused by PHP-FPM and now there gone, by adapting your configuration!

    THANK YOU SO MUCH!

    

Leave a Reply