Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

i am installing wnmp useing this link

i have followed the instruction but i got this is the error that i get from nginx error log.

the logs

1 upstream sent unsupported FastCGI protocol version: 70 while reading response header from upstream, client:, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://", host: "localhost"

heres my folder

- wnmp
  - memcached
  - mysql
  - nginx
  - php
  - www

my nginx.conf

#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/;

events {
    worker_connections  1024;

http {
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;

    server {
        listen       80;
        server_name  localhost;

        #charset koi8-r;

        #access_log  logs/host.access.log  main;

        location / {
            root   ../www;
            index  index index.html index.htm index.php;

        #error_page  404              /404.html;

        # redirect server error pages to the static page /50x.html
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;

        # proxy the PHP scripts to Apache listening on
        #location ~ \.php$ {
        #    proxy_pass;

        # pass the PHP scripts to FastCGI server listening on
        location ~ \.php$ {
            root           ../www;
            fastcgi_index  index.php;
            fastcgi_param  SCRIPT_FILENAME  ../www$fastcgi_script_name;
            include        fastcgi_params;

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #location ~ /\.ht {
        #    deny  all;

    # another virtual host using mix of IP-, name-, and port-based configuration
    #server {
    #    listen       8000;
    #    listen       somename:8080;
    #    server_name  somename  alias  another.alias;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }

    # HTTPS server
    #server {
    #    listen       443;
    #    server_name  localhost;

    #    ssl                  on;
    #    ssl_certificate      cert.pem;
    #    ssl_certificate_key  cert.key;

    #    ssl_session_timeout  5m;

    #    ssl_protocols  SSLv2 SSLv3 TLSv1;
    #    ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
    #    ssl_prefer_server_ciphers   on;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }


and btw heres the start.bat


REM Windows The following is not valid  

REM  Each process handles the maximum number of requests, or is set to Windows Environment variables  

:: Start PHP-fastcgi on port 9000
RunHiddenConsole php\php-cgi.exe -b -c php\php.ini

:: Start MySQL using the mysql\my.ini config file
start mysql\bin\mysqld

:: Start Memcached (m = memory to use in MB, c = max connections allowed)
RunHiddenConsole memcached\memcached.exe -m 10 -c 1024

:: Start the nginx server
cd nginx
start nginx


if there is anything that you need please comment

Thanks for looking in

Adam Ramadhan

share|improve this question

I had this problem too. Discovered that another application was listening on port 9000 already when I started php-cgi.exe. It seems that php-cgi.exe does not report this.

In my case it was, believe it or not "E Text-Editor" that was listening on port 9000. I found out this by running (elevated on Win7):

netstat -a -b -n

(the executeable listening is shown AFTER the port line)

So, killing that other app fixed the problem and changing the port number is a more long-term solution :) For me, anyway!

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.