Re: [ANN] SF Bay Area OpenResty Meetup

Oh I wish I could go, bit far to fly (from Aus) unfortunately. On Thu, Feb 4, 2016 at 9:07 AM, Yichun Zhang (agentzh) wrote: > Hi folks, > > I've recently created the Bay Area OpenResty Meeup group on meetup.com: > > http://www.meetup.com/Bay-Area-OpenResty-Meetup/ > > You're welcome to join

Re: nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)

> smsmaddy1981 [2016-02-04 00:03]: > > Requirement is to start NGinx other than root user > > 1) Added entry tp /etc/sudoers for specific user as below: > gvpALL=(ALL) NOPASSWD: ALL > > 2) Tried starting NGinx as gvp user, below error thrown: > nginx: [emerg] bind() to 0.0.0.0:80 failed (13: P

nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)

Requirement is to start NGinx other than root user 1) Added entry tp /etc/sudoers for specific user as below: gvpALL=(ALL) NOPASSWD: ALL 2) Tried starting NGinx as gvp user, below error thrown: nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied) 3) Some blog says: https://www.

Re: Restart Nginx than root user?

Hi Steve, Thanks for your email. And, Is the same solution what I have described in my initiated email. No luck there. Any other suggestions please? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,264087,264318#msg-264318 ___ nginx mailing

[ANN] SF Bay Area OpenResty Meetup

Hi folks, I've recently created the Bay Area OpenResty Meeup group on meetup.com: http://www.meetup.com/Bay-Area-OpenResty-Meetup/ You're welcome to join us in this group. We're currently planning a face-to-face meetup at 5:30pm ~ 6:30pm on 9 March 2016 in CloudFlare's office (101 Townsend

Re: question about client certs

On Wed, Feb 03, 2016 at 09:37:25AM +0100, Aleksandar Lazic wrote: > Am 02-02-2016 23:22, schrieb Alex Samad: Hi there, > Cool it would be nice if you can tell us if it's works and how was > your solution ;-) I think that "location" does not take variables, and so this will not work. More below.

Re: "upstream sent too big header while reading response header from upstream"?

Thanks, solved ;) BR, Rafal. 2016-02-03 14:42 GMT+01:00 Richard Stanway : > You want proxy_buffer_size. > > http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffer_size > > On Wed, Feb 3, 2016 at 2:24 PM, Rafał Radecki > wrote: > >> Hi All. >> >> I am currently trying to find the

Re: "upstream sent too big header while reading response header from upstream"?

You want proxy_buffer_size. http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffer_size On Wed, Feb 3, 2016 at 2:24 PM, Rafał Radecki wrote: > Hi All. > > I am currently trying to find the source of "upstream sent too big header > while reading response header from upstream" in m

"upstream sent too big header while reading response header from upstream"?

Hi All. I am currently trying to find the source of "upstream sent too big header while reading response header from upstream" in my logfiles because nginx as a consequence returns "502 Bad Gateway". Basically I used tcpdump to get the traffic and I compared two cases: 1) the communication is ok

Re: question about client certs

Am 02-02-2016 23:22, schrieb Alex Samad: Yep I think thats what i was asking. Cool it would be nice if you can tell us if it's works and how was your solution ;-) BR Aleks We have a home grown RP at work that does it and IIS used to do it, apply cert requirements on part of the tree. On