I get 400 bad request when client certs are used early even though I
have ssl_verify_client optional.
nginx: [info] 9612#0: *338 client SSL certificate verify error:
(9:certificate is not yet valid) while reading client request headers,
Is there anyway to ignore the time check?
__
On 27.06.2018 15:57, Ruslan Ermilov wrote:
> Since you have switched auth_basic off, the only enabled authentication
> left is by client address, and your inherited configuration says it's
> denied for everything except . Put "allow all" into the
> "location /.well-known/acme-challenge/" to hav
On Wed, Jun 27, 2018 at 03:08:50PM +0200, basti wrote:
> Hello,
> I have a config like:
>
> server {
>
> ...
> # combine basic auth and ip whitelisting
> #
> https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/
> satisfy any;
> allow ;
> deny
> On Jun 27, 2018, at 2:02 AM, Maxim Dounin wrote:
>
> Hello!
Hello again!
> On Wed, Jun 27, 2018 at 12:56:09AM -0400, VP Lists wrote:
>
> [...]
>
>> OK, here’s where things get interesting:
>>
>> On MacOS El Capitan:
>> --http-client-body-temp-path=/usr/local/var/run/nginx/client_body_te
Hello,
I have a config like:
server {
...
# combine basic auth and ip whitelisting
#
https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/
satisfy any;
allow ;
deny all;
auth_basic "Restricted";
auth_basic_user_file /etc/nginx/nx4/.htpass
Look into *proxy_read_timeout* *time*;
https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout
*proxy_connect_timeout* *time*;
https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_connect_timeout
On Wed, Jun 27, 2018 at 1:57 PM duda wrote:
> Hi
>
> I have one
Hi
I have one backend:
upstream backend_1 {
server 127.0.0.1:35510;
}
and server:
server {
...
location / {
proxy_pass http://backend_1;
}
}
Sometimes I have to restart my backend and it is unavailable for 3-5sec
(port unreachable)
How I can tell nginx to "wait" for backe
