premisses ------------- nginx version: nginx/1.7.10 TLS SNI support enabled Serving vhosts each vhost has own registered certificate each vhost works as expected task ----- Obtain 444 from ://<IP-ADDRESS>. case http://<IP-ADDRESS> -------------------------------------- configuration: server { listen 80; server_name _; root /devby 173279834462 - Nginx Mailing List - English
I am coming precisely from nginx 1.7.9 + libressl 2.1.3, configured as you mentioned. As 1.7.9 kept crashing, we downgraded to "stable" 1.6.4. Chapter closed then. We are back to 1.7.9... P.S. Did anybody note that the login to the forum does not use https?by 173279834462 - Nginx Mailing List - English
"no OpenSSL types or functions are exposed." http://www.openbsd.org/papers/eurobsdcon2014-libressl.htmlby 173279834462 - Nginx Mailing List - English
nginx-1.6.2 >make [...] ec/ec_curve.c:2918:2: warning: unused variable '_EC_GOST_2012_Test' [-Wunused-const-variable] _EC_GOST_2012_Test = { ^ 1 warning generated. Perhaps its defining block is best moved to the 1.7 branch.by 173279834462 - Nginx Mailing List - English
nginx-1.6.2 >make [...] src/event/ngx_event_openssl.c:2520:9: error: implicit declaration of function 'RAND_pseudo_bytes' is invalid in C99 [-Werror,-Wimplicit-function-declaration] RAND_pseudo_bytes(iv, 16); ^ 1 error generated. patch: perl -i.bak -0p -e 's|(^#include <ngx_event.h>).*(typedef struct)|$1\n#include <openssl\/rand\.h>\n\nint RAND_byteby 173279834462 - Nginx Mailing List - English
nginx 1.6.2 + libressl 2.1.3 >tail -f [...]/port-443/*.log ==> stderr.log <== 2015/02/01 01:35:34 15134#0: worker process 15139 exited on signal 11 2015/02/01 01:35:34 15134#0: shared memory zone "SSL" was locked by 15139 2015/02/01 01:35:42 15134#0: worker process 15138 exited on signal 11 2015/02/01 01:35:42 15134#0: shared memory zone "SSL" was lockedby 173279834462 - Nginx Mailing List - English
Hello, I seek advice on configuring nginx as a mail proxy. PREMISSES The existing system is based upon postfix and dovecot. The system delivers "n" virtual domains, say, mx.example_1.org, mx.example_2.org, ..., mx.example_n.org, all behind a single IP. There is no "shared" (Subject Alternative Name) certificate, because adding or releasing a domain would reby 173279834462 - Nginx Mailing List - English