geoip filtering not working

2013-07-12 Thread bignginxfan
Hello, I'm trying to figure out why Nginx's geoip modules doesn't seem to filter out certain ip's from a banned country. I manually tested the GeoIP.dat using 'geoiplookup' against a few ips that successfully connected but were in a banned country. GeoIP.dat was fine, it wasn't the problem. Maybe

Re: duplicating or forking incoming requests

2013-07-12 Thread Gary Foster
Thanks, that did the trick exactly! Now that I have something that works, I'm off to the docs to figure out where my fundamental misunderstandings were and correct them. Very much appreciated! -- Gary F. On Jul 12, 2013, at 1:04 PM, Maxim Dounin wrote: > Hello! > > On Fri, Jul 12, 2013 at 1

different fastcgi_cache for bots and humans

2013-07-12 Thread Ian M. Evans
As mentioned before, I'm tweaking pixabay's version of handling the new Google Image search traffic killer by making their trap URLs more cacheable. Img tags in the html will have ?i appended to the source and those "?i" are removed for bots. I thought I could use nginx's httpsubmodule to strip th

Re: duplicating or forking incoming requests

2013-07-12 Thread Maxim Dounin
Hello! On Fri, Jul 12, 2013 at 12:47:02PM -0700, Gary Foster wrote: [...] > Here's the configuration snippets I'm currently using: > > location = /events { > access_log events_access.log events_format; > expires 1s; > try_files @proxy @proxy; > # try_files @proxy /empty.html;

duplicating or forking incoming requests

2013-07-12 Thread Gary Foster
I'm trying to figure out how to accomplish something with nginx and it seems to have me baffled. We use nginx as an endpoint to log incoming events. The default response is a 200, empty body and an entry in the access log in a very specific format. For legacy reasons, this will not change any

Re: nginx debian 6 64bits

2013-07-12 Thread dumorim
tcp0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 2250/php-fpm.conf) excuse this post so it does not have editing Posted at Nginx Forum: http://forum.nginx.org/read.php?2,240765,240796#msg-240796 ___ nginx mailing list n

Re: nginx debian 6 64bits

2013-07-12 Thread dumorim
TCP localhost:9000 (LISTEN) php5-fpm 7820www-data0u IPv4 66000t0 TCP localhost:9000 (LISTEN) php5-fpm 7821www-data0u IPv4

Re: nginx debian 6 64bits

2013-07-12 Thread dumorim
ps axu www-data 14168 0.0 0.0 232088 10192 ?S19:16 0:00 php-fpm: pool w www-data 14169 0.0 0.0 234432 10748 ?S19:16 0:00 php-fpm: pool w www-data 14171 0.0 0.0 231552 7856 ?S19:16 0:00 php-fpm: pool w www-data 14172 0.0 0.0 231528 7704 ?

Re: nginx debian 6 64bits

2013-07-12 Thread dumorim
netstat -napt 6915/nginx: worker tcp0 0 109.236.87.68:80201.90.8.68:41544 ESTABLISHED 6911/nginx: worker tcp0 0 109.236.87.68:80189

Re: nginx debian 6 64bits

2013-07-12 Thread Host DL
execute bellow commands to check that it is runnung properly or not: ps axu | grep php or netstat -napt | grep LIST | grep :9000 On Fri, Jul 12, 2013 at 9:21 PM, dumorim wrote: > /etc/php5/fpm/pool.d www.conf > > ; Start a new pool named 'www'. >

Re: nginx debian 6 64bits

2013-07-12 Thread dumorim
/etc/php5/fpm/pool.d www.conf ; Start a new pool named 'www'. ; the variable $pool can we used in any directive and will be replaced by the ; pool name ('www' here) [www] ; Per pool prefix ; It only applies on the following directives: ; - 'slowlog' ; - 'listen' (unixsocket) ; - 'chroot' ; - 'chd

Re: nginx debian 6 64bits

2013-07-12 Thread Host DL
Check your php-fpm It doesn't seem to be responsible On Fri, Jul 12, 2013 at 9:13 PM, dumorim wrote: > 2013/07/12 18:34:55 [error] 26317#0: *1457 connect() failed (110: > Connection > timed out) while connecting to upstream, client: 258.32.219.11,

Re: nginx debian 6 64bits

2013-07-12 Thread dumorim
2013/07/12 18:34:55 [error] 26317#0: *1457 connect() failed (110: Connection timed out) while connecting to upstream, client: 258.32.219.11, server: exemple.com, request: "GET /announce.php?passkey=03583fb17481254a98419d4c34&info_hash=%E9%8A%17%27%19R%26%BD6%9C%1D%BF%E7%F8%2F%FF%DB%BC%BB%60&peer_id

Re: SSL + Large file uploads (3GB+)

2013-07-12 Thread FSC
At the end of the day the cause was a timeout due to long processing in the background. Thanks for having a look anyways! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,240727,240783#msg-240783 ___ nginx mailing list nginx@nginx.org http://m

Re: nginx debian 6 64bits

2013-07-12 Thread Maxim Dounin
Hello! On Thu, Jul 11, 2013 at 03:02:20PM -0400, dumorim wrote: [...] > erro > 502 bad gateway I guess the question is "Why the error is returned?". Answers to such questions usually can be found in the error log, try looking into it. -- Maxim Dounin http://nginx.org/en/donation.html

Reg: SCGI application deployment using NGINX

2013-07-12 Thread P Amarnath
Hi, I would like to know the procedure to deploy SCGI application in NGINX server. Thanks in advance -- With Best Regards, P Amarnath, IPNG - Cloud Storage, Global Edge Software Ltd. ___ nginx mailing list nginx@nginx.org http://mailman.ngi

Re: Problem with VPN IP address and Nginx

2013-07-12 Thread John Doe
From: wolfy > Nobody can help me? Maybe check the request headers...? JD ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Problem with VPN IP address and Nginx

2013-07-12 Thread wolfy
Nobody can help me? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,240709,240776#msg-240776 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: https redirect going to infinite loop

2013-07-12 Thread parulsood85
Hello Francis, Here is the curl o/p executed from browser machine. c:\curl>curl.exe -i http://example.com HTTP/1.1 301 Moved Permanently Content-Type: text/html Date: Fri, 12 Jul 2013 08:53:12 GMT Location: https://example.com Server: nginx/1.2.8 Content-Length: 184 Connection: keep-alive 301 M

Re: https redirect going to infinite loop

2013-07-12 Thread Francis Daly
On Fri, Jul 12, 2013 at 02:50:56AM -0400, parulsood85 wrote: Hi there, >server { > listen 80; > server_name example.com; So: nginx is not listening for https requests? > location / { > rewrite ^(.*) https://example.com permanent; >