Hello,
Thanks for the prompt reply.
I have scanned the listing ports in the servers. Please help me out to fix
this issue.
I never worked on Nginx server and am totally stuck.
# sudo nmap localhost
Starting Nmap 5.21 ( http://nmap.org ) at 2013-07-23 20:15 EDT
Nmap scan report for localhost (127
On Wed, Jul 24, 2013 at 03:49:05PM -0700, John Watson wrote:
Hi there,
> Upgraded from 1.2.9 to 1.4.1 and now started getting:
>
> [emerg] could not build the variables_hash, you should increase either
> variables_hash_max_size: 512 or variables_hash_bucket_size: 64
> adding this to http bl
Hi Axel,
Thank you for the reply. I have pasted some of my nginx.conf file below. Can
you conform if i'm setting proxy_next_upstream in correct location please?
Also, is there a way to have fail_timeout increment per fail? i.e if it
failed once try again in 30 secs as it might be minor issue, the
Upgraded from 1.2.9 to 1.4.1 and now started getting:
[emerg] could not build the variables_hash, you should increase either
variables_hash_max_size: 512 or variables_hash_bucket_size: 64
Same configuration and even dropped (2) 3rd party modules.
nginx.conf and ./configure params:
https://gist
Our nginx server is running on Heroku, which proxies SSL. This mostly
works fine, but nginx has one problem with it: since it thinks the protocol
is http, any redirects (such as trailing-slash redirects) go to http
instead of https.
The usual fix for this is X-Forwarded-Proto, but nginx doesn't s
That looks like an OpenERP problem: http://bit.ly/1aJm0DB
_Nik
On 7/24/2013 1:36 PM, imran_kh wrote:
> Hello,
>
> Thanks for the reply.
>
> Yes you are correct. I have tried to change the port from 8080 to 80 in
> /etc/nginx/conf.d/default.conf.
> Browse the Public IP address and xyz.com site, g
Hello,
Any suggestion or advice?
Thanks,
Imran Khan.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241157,241207#msg-241207
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
Thanks for the reply.
Yes you are correct. I have tried to change the port from 8080 to 80 in
/etc/nginx/conf.d/default.conf.
Browse the Public IP address and xyz.com site, getting “no handler found”
error.
File /etc/nginx/conf.d/default.conf content as follows.
# sudo cat default.conf
#
Hello @all,
Is it possible to define array / hashes in nginx? I have the following
idea:
nginx should check $arg_PARAMETER which is defined by an array. If the
right element in the array, then die access is permitted, otherwise
denied.
example:
the $arg_PARAMETER can have the following values:
Go back over all your nginx conf files, making sure to look at included
files as well... it seems that somewhere you have "listen 8080" and
possibly overlapping "server_name" directives.
If that fails, I'd suggest you backup then throw out your current
config, then start simple and build it up one
Hello,
I have observed that, Nginx configured on port 80 as per
/etc/nginx/sites-enabled/default file but it is listening on port 8080 and
80. Please see the details for the same.
server {
listen 80;
server_name example.com;
location / {
proxy_pass http://localhost:8009;
send_timeout 6000;
proxy
On 23 Jul2013, at 18:10 , inspiron wrote:
> here are those outputs : http://pastebin.com/0Epq6KGj
>
> the above output is for nginx 1.4.1 if i update to 1.4.2 i loose nearly half
> of those lines in nginx -v output including geoip and etc.
Your 1.4.1 package is probably from atomic repo.
We w
Hi,
I'm trying to diagnose a problem we have on a rather complex system with
an nginx acting as a remote proxy server, where what appears to be a
completely empty response is being returned, seemingly from the nginx
cache. It's early days yet in my troubleshooting, so this may not
actually be
David Gwynne Wrote:
---
> i am also experiencing this problem running 1.4.2.
Hi David. The response I got from my Valentin off-list was that there is a
known incompatibility with SPDY and proxy cache, due to the way proxy cache
will kill the con
Hey Maxim,
>> I've made a patch for this issue a while ago:
>> http://mailman.nginx.org/pipermail/nginx-devel/2012-December/003152.html
>
> I believe I've already reviewd this patch and explained why it's
> wrong.
Yes, you did... But fixing it ended very low on my TODO list.
I just pointed it to
Hello!
On Tue, Jul 23, 2013 at 06:47:46PM -0700, Piotr Sikora wrote:
> Hello,
> I've made a patch for this issue a while ago:
> http://mailman.nginx.org/pipermail/nginx-devel/2012-December/003152.html
I believe I've already reviewd this patch and explained why it's
wrong.
--
Maxim Dounin
http
16 matches
Mail list logo
