António P. P. Almeida

I don't think that will work because upstream doesn't handle variables AFAIK. I would use two different locations that have different upstreams, yeah it's ugly, but it should work :(

Sure. It means that nginx cannot find an upstream named www0. The upstream configurations were missing. I just [pushed](https://github.com/perusio/drupal-with-nginx/commit/f618d345fc508d00187338a75fd8abbfb7d0378c) the fix. Try it out please. Thanks

Hmm. Seems like this is something related to solr. Can you get a [debug log](http://nginx.org/en/docs/debugging_log.html) and paste it on a Gist? Thanks,

Why do you need that? Do you allow for anonymous users to upload files? Yes you can add regexes to map. Just add another map directive and modify the final...

Hello, Thanks for your question. This has a very simple solution. Try this: ``` nginx ## Advanced Help module makes each module provided README available. location ^~ /help/ { location...

Hmm, Can you provide a [debug log](nginx.org/en/docs/debugging_log.html) tracing the requests that generate the 502? Paste it here or in a paste bin somewhere. Thanks,

Ok. If the problem is only with thw Ajax calls is quite simple to solve. Add the following location to the `drupal.conf` and/or `drupal6.conf` file: ``` nginx location ^~ /system/ajax...

Well then the problem is different because we need to match the `$arg_q` variable with anything ending with `/autocomplete`. Hmm. The quick temporary fix is to comment out the `internal`...

@andythornton @rfay the `internal` keyword is a [nginx special directive](http://nginx.org/en/docs/http/ngx_http_core_module.html#internal) that only allows access to a given location (URL) from **whitin** the server. You won't be able to access `index.php`...

@sb56637 @heidiblobaum there's no _great_ issue in commenting out the `internal` directive. Don't rollback. This directive is just a **nice to have thing**.