PHP-FPM and Nginx: 502 Bad Gateway

**Configuration** - Ubuntu Server 11.10 64 bit - Amazon AWS, Ec2, hosted on the cloud - t1.micro instance Before I write anything else, I'd like to state that I've checked both [nginx 502 bad gateway][1] and [Nginx + PHP-FPM 502 Bad Gateway][2] threads, which unfortunately haven't helped me in this regard. The issue appears to be rather common: a misconfiguration of nginx or php-fpm can lead to a `502 Bad Gateway` error, which is something that I haven't been able to get rid of. Note that this appears *even when I go to my domain root*, without specifying any particular directory. I'm running an Amazon EC2 webserver, with port 9000 enabled, port 80 open, etc. The question in particular is, how can I get rid of this nasty error? Or, better yet, how can I get `php5-fpm` to *actually work*. **What I Have Attempted so Far** Mostly consistent editing of configuration files, notably `php-fpm.conf` and `nginx.conf`. **i.** *php-fpm.conf* I've added the following, which hasn't quite helped much: ;;;;;;;;;;;;; ; Fpm Start ; ;;;;;;;;;;;;; ;pm.start_servers = 20 ;pm.min_spare_servers = 5 ;pm.max_spare_servers = 35 Now, afterward I tried including my configuration files: `include=/etc/php5/fpm/*.conf` Which only screwed me even further. ***Full Configuration*** ;;;;;;;;;;;;;;;;;;;;; ; FPM Configuration ; ;;;;;;;;;;;;;;;;;;;;; ; All relative paths in this configuration file are relative to PHP's install ; prefix (/usr). This prefix can be dynamicaly changed by using the ; '-p' argument from the command line. ; Include one or more files. If glob(3) exists, it is used to include a bunch of ; files from a glob(3) pattern. This directive can be used everywhere in the ; file. ; Relative path can also be used. They will be prefixed by: ; - the global prefix if it's been set (-p arguement)...