Quantcast
Channel: Nginx Forum - Nginx Mailing List - English
Viewing all 7229 articles
Browse latest View live

nginx reverse proxy with subdomains not working with docker containers (no replies)

$
0
0
Hello, I am quite desperate.

| I am running nginx as reverse proxy directly installed on the server. For an error analysis I created two similar containers listening on port 83 and 84. These two containers should be accessed by two different subdomains.If I am accessing cops-adress it works awsome if I am doing the same with the pydio-adress it ends up in a connection failiure and URL is changes to https://localhost.I have no idea what to change to get it running.This is my site.conf
server {
listen 80;
server_name myserveradress.de pydio.myserveradress.de cops.myserveradress.de;

return 301 https://$host$request_uri;

## Disable viewing .htaccess & .htpassword
location ~ /\.ht {
deny all;
}
root /var/www;
access_log /var/log/nginx/access_proxy.log;
error_log /var/log/nginx/error_proxy.log info;

location ^~ /.well-known/acme-challenge {
proxy_pass http://127.0.0.1:81;
proxy_redirect off;
}

}
server {
listen 443 ssl;
server_name myserveradress.de;
root /var/www;

ssl on;
ssl_certificate /etc/letsencrypt/live/myserveradress.de/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/myserveradress.de/privkey.pem;
ssl_protocols TLSv1.2;
ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK';
ssl_dhparam /etc/nginx/ssl/dhparams.pem;
ssl_ecdh_curve secp384r1;
ssl_prefer_server_ciphers on;
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/letsencrypt/live/myserveradress.de/fullchain.pem;
ssl_session_timeout 24h;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
# Add headers to serve security related headers
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
# location = / {
# Disable access to the web root, otherwise nginx will show the default site here.
# deny all;
# }
################################################################################################
location ^~ /rpimonitor {

proxy_connect_timeout 300;
proxy_send_timeout 300;
proxy_read_timeout 300;
send_timeout 300;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_pass http://127.0.0.1:8888;
proxy_redirect off;
}

#########################################################################
location ^~ /owncloud {
client_max_body_size 1G;
proxy_connect_timeout 300;
proxy_send_timeout 300;
proxy_read_timeout 300;
send_timeout 300;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_pass http://192.168.100.55:80;
proxy_redirect off;
}

}
##########################################################################

server {
listen 443 ssl;
server_name cops.myserveradress.de;
root /var/www;
access_log /var/log/nginx/cops_access.log;
error_log /var/log/nginx/cops_error.log info;

ssl on;
ssl_certificate /etc/letsencrypt/live/cops.myserveradress.de/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/cops.myserveradress.de/privkey.pem;
ssl_protocols TLSv1.2;
ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK';
ssl_dhparam /etc/nginx/ssl/dhparams.pem;
ssl_ecdh_curve secp384r1;
ssl_prefer_server_ciphers on;
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/letsencrypt/live/cops.myserveradress.de/fullchain.pem;
ssl_session_timeout 24h;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
# Add headers to serve security related headers
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;

location ^~ / {

auth_basic "Restricted"; # Ausgabe-Meldung bei Zugriff
auth_basic_user_file /etc/nginx/.htpasswd; # Pfad zur .htpasswd-Datei
proxy_connect_timeout 300;
proxy_send_timeout 300;
proxy_read_timeout 300;
send_timeout 300;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_pass http://127.0.0.1:83;
proxy_redirect off;
}

}


#################################################################################################################

server {
listen 443 ssl;
server_name pydio.myserveradress.de;
root /var/www;
# access_log /var/log/nginx/cops_access.log;
# error_log /var/log/nginx/cops_error.log info;

ssl on;
ssl_certificate /etc/letsencrypt/live/pydio.myserveradress.de/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/pydio.myserveradress.de/privkey.pem;
ssl_protocols TLSv1.2;
ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK';
ssl_dhparam /etc/nginx/ssl/dhparams.pem;
ssl_ecdh_curve secp384r1;
ssl_prefer_server_ciphers on;
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/letsencrypt/live/pydio.myserveradress.de/fullchain.pem;
ssl_session_timeout 24h;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
# Add headers to serve security related headers
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;


location ^~ / {

auth_basic "Restricted"; # Ausgabe-Meldung bei Zugriff
auth_basic_user_file /etc/nginx/.htpasswd; # Pfad zur .htpasswd-Datei
proxy_connect_timeout 300;
proxy_send_timeout 300;
proxy_read_timeout 300;
send_timeout 300;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_pass http://127.0.0.1:84;
proxy_redirect off;
}

}
A strange thing I find nothing in error logs. Thanks for your help |

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

HTTP To TCP Conversion (no replies)

$
0
0
Hi,

I am planning to use Nginx as a webserver to the front end of my susbcriber tasks (1:N, 1 Rest Server for N Subscriber Tasks). The communication between the Nginx and my tasks would be over TCP. So, when the Nginx receives the HTTP messages, it will parse the message and then put to those registerd TCP clients. Any idea how can this be done.
Thanks, Santos

Question about custom error pages (2 replies)

$
0
0
Hi

How would I added custom info to the error page.

Say like for 400 if its a cert error, how can I add that to the page and
maybe to add in the clients ip address as well

A
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Number of memory for reload (no replies)

$
0
0
Hi,

Is there a possibility to get number of memory which required to reloading nginx workers?

Thank you

Re: [nginx-announce] nginx-1.11.11 (no replies)

$
0
0
Hello Nginx users,

Now available: Nginx 1.11.11 for Windows
https://kevinworthington.com/nginxwin11111
(32-bit and 64-bit versions)

These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are at
nginx.org.

Announcements are also available here:
Twitter http://twitter.com/kworthington
Google+ https://plus.google.com/+KevinWorthington/

Thank you,
Kevin
--
Kevin Worthington
kworthington *@* (gmail] [dot} {com)
http://kevinworthington.com/
http://twitter.com/kworthington
https://plus.google.com/+KevinWorthington/

On Tue, Mar 21, 2017 at 11:19 AM, Maxim Dounin <mdounin@mdounin.ru> wrote:

> Changes with nginx 1.11.11 21 Mar
> 2017
>
> *) Feature: the "worker_shutdown_timeout" directive.
>
> *) Feature: vim syntax highlighting scripts improvements.
> Thanks to Wei-Ko Kao.
>
> *) Bugfix: a segmentation fault might occur in a worker process if the
> $limit_rate variable was set to an empty string.
>
> *) Bugfix: the "proxy_cache_background_update",
> "fastcgi_cache_background_update", "scgi_cache_background_update",
> and "uwsgi_cache_background_update" directives might work
> incorrectly
> if the "if" directive was used.
>
> *) Bugfix: a segmentation fault might occur in a worker process if
> number of large_client_header_buffers in a virtual server was
> different from the one in the default server.
>
> *) Bugfix: in the mail proxy server.
>
>
> --
> Maxim Dounin
> http://nginx.org/
> _______________________________________________
> nginx-announce mailing list
> nginx-announce@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-announce
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

fastcgi_pass and http upstream (2 replies)

$
0
0
Hi,

is is possible to have a upstream that contains point to http and phpfpm?





Kind Regards,
Vucomir Ianculov
E-Mail: vukomir@ianculov.ro
Phone: (+40) 722 - 690 - 514
View Vucomir Ianculov's profile on LinkedIn

Vucomir Ianculov

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Nginx-lua Dynamic location to upstream (no replies)

$
0
0
Hi there,
I've Just started to play with Lua (with nginx-plus) and this is what I'd like to achieve:
I expose a location and a lua script Will inspect http args.Once It takes the args,It Will call an external api searching for a specific content and It Will writes the returned json values on some lua variables.
Based on the returned values,Nginx Will proxy_pass to the right upstream.
Does Nginx/luajit cache all json values/pages based on different calls?I don't really want to call an external api for every single location request...
Thanks a lot.

302 301 redirect custom HTML content (no replies)

$
0
0
Hello!

I'm trying to
1. send people to home page if they enter wrong place (404)
2. it works, but HTML content with headers is:

HTTP/1.1 302 Moved Temporarily
Server: nginx/1.10.3
Date: Thu, 23 Mar 2017 11:38:08 GMT
Content-Type: text/html
Content-Length: 161
Location: http://mysite/myhomepage.html
Connection: keep-alive

<html>
<head><title>302 Found</title></head>
<body bgcolor="white">
<center><h1>302 Found</h1></center>
<hr><center>nginx/1.10.3</center>
</body>
</html>


Is it possible to send custom page content?

My config:

server {
listen 80;
root /somewhere/mysite;
location @redirect_to_home {
error_page 302 /custom_302_page.html;
return 302 /myhomepage.html;
}
error_page 404 = @redirect_to_home;
}


Thanks for the advise!
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

回复:Nginx-lua Dynamic location to upstream (no replies)

$
0
0
You can refer to the open source Openresty.
----- 原始邮件 -----
发件人:"nembo" <nginx-forum@forum.nginx.org>
收件人:nginx@nginx.org
主题:Nginx-lua Dynamic location to upstream
日期:2017年03月23日 18点24分


Hi there,
I've Just started to play with Lua (with nginx-plus) and this is what I'd
like to achieve:
I expose a location and a lua script Will inspect http args.Once It takes
the args,It Will call an external api searching for a specific content and
It Will writes the returned json values on some lua variables.
Based on the returned values,Nginx Will proxy_pass to the right upstream.
Does Nginx/luajit cache all json values/pages based on different calls?I
don't really want to call an external api for every single location
request...
Thanks a lot.
Posted at Nginx Forum: https://forum.nginx.org/read.php?2,273136,273136#msg-273136
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Custom Error pages (no replies)

$
0
0
Hi

I got something like this

error_page 404 /stderror404.html;

location = /stderror400.html {
root /var/www/error;
content_by_lua_file /var/www/error/stderror400.lua;

internal;
allow all;
}


and the lua file has

ngx.say( "Your source ip address is: " .. ngx.var.remote_addr .. ":" ..
ngx.var.remote_port .. "<br>");
ngx.say( "You requested URI: " .. ngx.var.uri .. "<br>");


Question

Seems like I have to do a restart to get the lua file reread if I have
changed it ... reload doesn't seem to cut it. is there some signal i can
send to reread the lua file.

ngx.var.uri is always /stderror404.html how can I capture the original uri
and print it here ?
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

100% CPU use in ngx_http_finalize_connection (5 replies)

$
0
0
Hello,
I recently moved our site to a new server running Linux 4.9, Debian
8.7 64 bit with nginx 1.11.11 from the nginx repository. Our config is
straightforward - epoll, a few proxy backends and a few fastcgi
backends, a handful of vhosts, some with HTTP2, geoip module loaded.
No AIO, no threads, no timer_resolution.

After some time, nginx worker processes are getting stuck at 100% CPU
use in what seems to be ngx_http_finalize_connection. New requests
hitting the worker are completely stalled. Eventually all nginx
workers will become stuck and the sites become unreachable.

I'm running older versions of nginx on the same versions of Debian and
Linux at other sites without a problem, but the server giving me
problems also receives a much larger amount of traffic than the
others. Due to the traffic, the debug log gets incredibly large which
makes it difficult to isolate the error. I've posted a 1 second
excerpt of the core debug log at http://pastebin.com/hqzGzjTV during
the time that some of the workers were at 100%, however I'm not sure
this contains enough information. I'll look into enabling HTTP level
logging if necessary.

Has anyone experienced anything similar to this or have any ideas
where to start looking to debug this?

Thanks.

nginx version: nginx/1.11.11
built by gcc 4.9.2 (Debian 4.9.2-10)
built with OpenSSL 1.0.1t 3 May 2016
TLS SNI support enabled
configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx
--modules-path=/usr/lib/nginx/modules
--conf-path=/etc/nginx/nginx.conf
--error-log-path=/var/log/nginx/error.log
--http-log-path=/var/log/nginx/access.log
--pid-path=/var/run/nginx.pid --lock-path=/var/run/nginx.lock
--http-client-body-temp-path=/var/cache/nginx/client_temp
--http-proxy-temp-path=/var/cache/nginx/proxy_temp
--http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp
--http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp
--http-scgi-temp-path=/var/cache/nginx/scgi_temp --user=nginx
--group=nginx --with-compat --with-file-aio --with-threads
--with-http_addition_module --with-http_auth_request_module
--with-http_dav_module --with-http_flv_module
--with-http_gunzip_module --with-http_gzip_static_module
--with-http_mp4_module --with-http_random_index_module
--with-http_realip_module --with-http_secure_link_module
--with-http_slice_module --with-http_ssl_module
--with-http_stub_status_module --with-http_sub_module
--with-http_v2_module --with-mail --with-mail_ssl_module --with-stream
--with-stream_realip_module --with-stream_ssl_module
--with-stream_ssl_preread_module --with-cc-opt='-g -O2
-fstack-protector-strong -Wformat -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -fPIC' --with-ld-opt='-Wl,-z,relro -Wl,-z,now
-Wl,--as-needed -pie'


#0 0x000055d533ab87e8 in ngx_pfree (pool=0x55d536202fe0,
p=0x55d5361636c0) at src/core/ngx_palloc.c:282
#1 0x000055d533af54d9 in ngx_http_set_keepalive (r=<optimized out>)
at src/http/ngx_http_request.c:3000
#2 ngx_http_finalize_connection (r=<optimized out>) at
src/http/ngx_http_request.c:2556
#3 0x000055d533af0d8b in ngx_http_core_content_phase
(r=0x55d536136f10, ph=0x55d537cbf210) at
src/http/ngx_http_core_module.c:1391
#4 0x000055d533aeb29d in ngx_http_core_run_phases
(r=r@entry=0x55d536136f10) at src/http/ngx_http_core_module.c:860
#5 0x000055d533aeb392 in ngx_http_handler (r=r@entry=0x55d536136f10)
at src/http/ngx_http_core_module.c:843
#6 0x000055d533af669e in ngx_http_process_request (r=0x55d536136f10)
at src/http/ngx_http_request.c:1921
#7 0x000055d533adeda4 in ngx_epoll_process_events (cycle=<optimized
out>, timer=<optimized out>, flags=<optimized out>) at
src/event/modules/ngx_epoll_module.c:902
#8 0x000055d533ad5caa in ngx_process_events_and_timers
(cycle=cycle@entry=0x55d5357ba110) at src/event/ngx_event.c:242
#9 0x000055d533adcc31 in ngx_worker_process_cycle
(cycle=cycle@entry=0x55d5357ba110, data=data@entry=0x12) at
src/os/unix/ngx_process_cycle.c:749
#10 0x000055d533adb583 in ngx_spawn_process
(cycle=cycle@entry=0x55d5357ba110, proc=proc@entry=0x55d533adcbb0
<ngx_worker_process_cycle>, data=data@entry=0x12,
name=name@entry=0x55d533b71db0 "worker process",
respawn=respawn@entry=-4) at src/os/unix/ngx_process.c:198
#11 0x000055d533adce50 in ngx_start_worker_processes
(cycle=0x55d5357ba110, n=24, type=-4) at
src/os/unix/ngx_process_cycle.c:358
#12 0x000055d533addae7 in ngx_master_process_cycle
(cycle=0x55d5357ba110) at src/os/unix/ngx_process_cycle.c:243
#13 0x000055d533ab5e56 in main (argc=<optimized out>, argv=<optimized
out>) at src/core/nginx.c:375
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

nginx-1.11.12 (no replies)

$
0
0
Changes with nginx 1.11.12 24 Mar 2017

*) Bugfix: nginx might hog CPU; the bug had appeared in 1.11.11.


--
Maxim Dounin
http://nginx.org/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Nginx cookie map regex remove + character (no replies)

$
0
0
So this is my map

map $http_cookie $session_id_value {
default '';
"~^.*[0-9a-f]{32}\=(?<session_value>[\w]{1,}+).*$" $session_value;
}


The cookie name = a MD5 sum the full / complete value of the cookie seems to cut of at a plus + symbol

What would the correct regex to be to ignore / remove + symbols from "session_value"

nginx 1.11.12 + nginScript = failed to restart nginx server (no replies)

$
0
0
Nginx compiles successfully with nginScript as a dynamic module.

nginx -V
nginx version: nginx/1.11.12
built by clang 3.4.2 (tags/RELEASE_34/dot2-final)
built with LibreSSL 2.4.5
TLS SNI support enabled
configure arguments: --with-ld-opt='-lrt -ljemalloc -Wl,-z,relro -Wl,-rpath,/usr/local/lib' --with-cc-opt='-m64 -mtune=native -mfpmath=sse -g -O3 -fstack-protector -fuse-ld=gold --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wno-sign-compare -Wno-string-plus-int -Wno-deprecated-declarations -Wno-unused-parameter -Wno-unused-const-variable -Wno-conditional-uninitialized -Wno-mismatched-tags -Wno-sometimes-uninitialized -Wno-parentheses-equality -Wno-tautological-compare -Wno-self-assign -Wno-deprecated-register -Wno-deprecated -Wno-invalid-source-encoding -Wno-pointer-sign -Wno-parentheses -Wno-enum-conversion -Wno-c++11-compat-deprecated-writable-strings -Wno-write-strings -gsplit-dwarf' --sbin-path=/usr/local/sbin/nginx --conf-path=/usr/local/nginx/conf/nginx.conf --with-http_stub_status_module --with-http_secure_link_module --with-libatomic --with-http_gzip_static_module --add-dynamic-module=../ngx_brotli --with-http_sub_module --with-http_addition_module --with-http_image_filter_module=dynamic --with-http_geoip_module --add-dynamic-module=../njs/nginx --with-stream_geoip_module --with-stream_realip_module --with-stream_ssl_preread_module --with-threads --with-stream=dynamic --with-stream_ssl_module --with-http_realip_module --add-dynamic-module=../ngx-fancyindex-0.4.0 --add-module=../ngx_cache_purge-2.3 --add-module=../ngx_devel_kit-0.3.0 --add-module=../set-misc-nginx-module-0.31 --add-module=../echo-nginx-module-0.60 --add-module=../redis2-nginx-module-0.13 --add-module=../ngx_http_redis-0.3.7 --add-module=../memc-nginx-module-0.17 --add-module=../srcache-nginx-module-0.31 --add-module=../headers-more-nginx-module-0.32 --with-pcre=../pcre-8.40 --with-pcre-jit --with-zlib=../zlib-1.2.11 --with-http_ssl_module --with-http_v2_module --with-openssl=../libressl-2.4.5

But I've tried both the example nginScript configurations at https://www.nginx.com/blog/introduction-nginscript/ as well as example posted at http://nginx.org/en/docs/http/ngx_http_js_module.html.

But both fail to restart nginx server with no indication as to why https://community.centminmod.com/posts/46868/

nginx -t
nginx: configuration file /usr/local/nginx/conf/nginx.conf test failed

is all I see nothing else ?

loaded nginScript module as a dynamic module via include file /usr/local/nginx/conf/dynamic-modules.conf in nginx.conf

cat /usr/local/nginx/conf/dynamic-modules.conf

load_module "modules/ngx_http_image_filter_module.so";
load_module "modules/ngx_http_fancyindex_module.so";
load_module "modules/ngx_http_brotli_filter_module.so";
load_module "modules/ngx_http_brotli_static_module.so";
load_module "modules/ngx_stream_module.so";
load_module "modules/ngx_http_js_module.so";
load_module "modules/ngx_stream_js_module.so";


nginx.conf excerpt

user nginx nginx;
worker_processes 4;
worker_priority -10;

worker_rlimit_nofile 260000;
timer_resolution 100ms;

pcre_jit on;
include /usr/local/nginx/conf/dynamic-modules.conf;


pid logs/nginx.pid;

events {
worker_connections 10000;
accept_mutex off;
accept_mutex_delay 200ms;
use epoll;
#multi_accept on;
}


http {

Strange LAN access error (1 reply)

$
0
0
On my LAN I have 3 windows 10 pc's, 1 Linux PC( Fedora 25 with apache2),
1 Raspberry Pi2b (Moode audio) and 2 Raspberry Pi3B's( NGINX), all
behind a TalkTalk router with a mixture of ethernet and Wi-Fi links. One
of the Pi3B's is running Cumulus software linked to a weather station
and has a nginx sever hosting a weather web site
(www.craythorneweather.info) The other Pi3B has a nginx server acting as
proxy server to pass weather requests to the weather Pi3 or to a
community site on the fedora machine as appropriate. The second Pi3 in
addition to acting as a proxy server also hosts its own (development)
web site.

I can get to all the web sites externally from the WAN but have hit a
snag accessing locally on the LAN. Using a browser (Firefox) on one of
the pc's I can get to the Fedora server or the weather Pi3 server using
the LAN ip address without a problem, if I try the lan address of the
other Pi3 the browser appends www.craythorneweather.info many hundreds
of times to the URI until I get a '414 Request-URI Too Large' error
message from the nginx server (1.10.3).

Any help getting to the bottom of this problem would be greatly appreciated.

Thanks,

Joe Curtis

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Re: [nginx-announce] nginx-1.11.12 (no replies)

$
0
0
Hello Nginx users,

Now available: Nginx 1.11.12 for Windows
https://kevinworthington.com/nginxwin11112
(32-bit and 64-bit versions)

These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are at
nginx.org.

Announcements are also available here:
Twitter http://twitter.com/kworthington
Google+ https://plus.google.com/+KevinWorthington/

Thank you,
Kevin
--
Kevin Worthington
kworthington *@* (gmail] [dot} {com)
http://kevinworthington.com/
http://twitter.com/kworthington
https://plus.google.com/+KevinWorthington/

On Fri, Mar 24, 2017 at 11:19 AM, Maxim Dounin <mdounin@mdounin.ru> wrote:

> Changes with nginx 1.11.12 24 Mar
> 2017
>
> *) Bugfix: nginx might hog CPU; the bug had appeared in 1.11.11.
>
>
> --
> Maxim Dounin
> http://nginx.org/
> _______________________________________________
> nginx-announce mailing list
> nginx-announce@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-announce
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

SSL client certyficage (2 replies)

$
0
0
Hi.
I have own cloud server with ssl client cert verification ssl_verify_client set to on. How I can disable verification for location/index.php/s/ share links ?

How to exact match a nginx location? (1 reply)

$
0
0
| I am configuring a nginx revser proxy. The result should be when user type http://10.21.169.13/mini, then the request should be proxy_pass to 192.168.1.56:5000. Here is the nginx config:server {
listen 80;
server_name 10.21.169.13;

location = /mini {
proxy_pass http://192.168.1.65:5000;
include /etc/nginx/proxy_params;
}
}
The above location block never worked with http://10.21.169.13/mini. The only location block worked is:server {
listen 80;
server_name 10.21.169.13;

location / {
proxy_pass http://192.168.1.65:5000;
include /etc/nginx/proxy_params;
}
}
But the above config also match http://10.21.169.13 request which is too board. What kind of location block will only match 'http://10.21.169.13/mini` and no more? |

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

UDP TLS Termination (2 replies)

$
0
0
Hi guys,

We are interested in UDP TLS Termination, any updates about this feature? I think I saw such topic on forum few moths ago, but I'm unable to find it now.

curl 301 moved permanently if I don't use slash at the end of the url (no replies)

$
0
0
Hi,

I need to list the content of some directories with curl without to use a '/' at the end of the url.

If I do not use the slash then I receive the message below, otherwise the content is showed. I tried many rewrite rules without success.

[user@localhost ~]$ curl http://mydomain.example.com/data/foo

<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>


[user@localhost ~]$ curl http://mydomain.example.com/data/foo/

<html>
<head><title>Index of /data/foo/</title></head>
<body bgcolor="white">
<h1>Index of /data/foo/</h1><hr><pre><a href="../">../</a>
<a href="57581/">57581/</a> 12-Jul-2016 01:56 -
<a href="57582/">57582/</a> 13-Jul-2016 01:55 -
<a href="57583/">57583/</a> 14-Jul-2016 00:34 -
</pre><hr></body>
</html>


This is my vhost configuration:

server {
listen 80;
server_name mydomain.example.com;
access_log /var/log/nginx/mydomain.example.com-access.log;
error_log /var/log/nginx/mydomain.example.com-error.log error;

location /data/foo {
alias /data/foo;
autoindex on;
}

location /data/bit {
alias /data/bit;
autoindex on;
}


Thanks.
Viewing all 7229 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>