Ok, yes, that's what I was seeing. Thanks for the info!
_Nik
On 9/14/2015 11:58:13 PM, itpp2012 wrote:
You mean something like:
[09/Sep/2015:20:21:38 +0200] 52.88.xxx.yyy z - - http
"\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
I experienced a problem with a web server earlier today in which it stopped
responding to all HTTP requests (they would just hang... not sure if they
connected and then hung, or got stuck trying to connect...). I'm not sure this
was even an Nginx issue (I had problems SSHing to the server and ev
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
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
Are there supposed to be services running on ports 8002 and 8007? If so,
then they don't seem to actually be running and you need to fix that
(that's not nginx-related). If you actually meant to proxy to another
port(s), then look at your nginx config, find where you're proxying to
8002 and 8007 an
If 8009 is the desired port, then change the upstream server in your
nginx conf to use port 8009. If 8002/8007 are the correct ports, then
change the upstream server to listen on those ports.
_Nik
On 7/23/2013 5:44 PM, imran_kh wrote:
> Hello,
>
> Correct. So how should I resolve this issue?
>
>
Note that the log entries from your previous email indicate upstream
servers on ports 8002 and 8007. According to what you've posted here,
there's nothing listening on either of those ports.
_Nik
On 7/23/2013 5:20 PM, imran_kh wrote:
> Hello,
>
> Thanks for the prompt reply.
>
> I have scanned th
"502 Bad Gateway" almost always means something is wrong with the
upstream server (i.e., Nginx is working fine, whatever it's proxying to
is having problems) so look for a problem there.
_Nik
On 7/23/2013 4:41 PM, imran_kh wrote:
> Hello,
>
> Thanks for the reply,
>
> Actually openerp is also hos
The "www" part is probably causing a problem too. As the regex is
written it will only match "www..." which I'm
guessing isn't what you intent. I would instead treat "www" as another
possible subdomain.
~^(?[^\.]*\.)?(?[^\.]*)\.(?[^\.*)$
Note I haven't tested this, but it's similar to a pattern I
Check your subdomain regex. Right now, if will only work if your
subdomain is a dot ;)
It should be (?[^\.]*) or (?[^\.]+)
_Nik
On 3/26/2013 5:56 AM, huttarichard wrote:
> Hi guys,
>
> I have question. My server_name looks like this:
>
> server_name ~^(www\.)(?[^\.]*)\.(?[^\.]*)$;
>
> but I nee
In my experience, Nginx returns 502 when the upstream server (Unicorn in
your case) doesn't respond or terminates the connection unexpectedly.
_Nik
On 3/19/2013 1:29 PM, fastcatch wrote:
> I have an application behind nginx (Rails on Unicorn if it matters) which
> listens on a UNIX socket.
>
> It
I haven't tried it yet, but nginx-push-stream-module looks good:
https://github.com/wandenberg/nginx-push-stream-module
_Nik
On 3/15/2013 4:24 PM, djczaski wrote:
> What are the best options for websocket backends? I'm working with an
> embedded platform so I'm somewhat restricted to something l
12 matches
Mail list logo
