3

Nginx Not Logging https / :443 Requests

view full story
linux-howto

http://serverfault.com – I am in the process of trying to configure a Server with https and for some reason it seems the requests are not hitting nginx at all. I have everything working properly but once I go to enable ssl it gives me an will not accept any requests on port 443 (connection timeout). Does anyone know how I can begin to debug this issue? I am using all of the same logic I have used on previous servers. Nginx.conf: user nginx; worker_processes 1; error_log /var/log/nginx/error.log warn; pid /var/run/nginx.pid; events { worker_connections 1024; } http { port_in_redirect off; (HowTos)

grtyyu's picture
Submitted by grtyyu on 06/15/2012 – Made popular on 06/15/2012

Stories similar to Nginx Not Logging https / :443 Requests

I have gzip enabled on nginx 1.2.8, but for some reason, it is not gzipping anything.

Nginx install info:

nginx version: nginx/1.2.8 built by gcc 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) TLS SNI support enabled configure arguments: --prefix=/usr/local/nginx-1.2.8 --with-http_ssl_module --with-http_realip_module --with-http_gzip_static_module --with-pcre --conf-path=/etc/nginx/nginx.conf --add-modul

I have followed instruction for setting up django with nginx from the django wiki (https://code.djangoproject.com/wiki/DjangoAndNginx) and have nginx setup as follows (a few name changes to fit my setup).

user nginx nginx;

worker_processes 2;

error_log /var/log/nginx/error_log info;

events { worker_connections 1024; use epoll; }

http { include /etc/nginx/mime.types;

I am having issues with my phpmyadmin on my nginx install.

When I enter <ServerIP>/phpmyadmin and logs in, I get redirected to <ServerIP>/index.php?<tokenstuff> instead of <ServerIP>/phpmyadmin/index.php?<tokenstuff>

Nginx config file:

user nginx; worker_processes 5;

error_log /var/log/nginx/error.log warn; pid /var/run/nginx.pid;

events { worker_c

On a Amazon EC2 instance we have nginx and tomcat running. Nginx is proxying all requests to tomcat on port 8080 running on the same instance.

This worked fine for a day, but then started seeing a lot of "upstream timed out (110: Connection timed out)" errors in the nginx logs and the site was inaccessible. Now tomcat is accessible all right at port 8080.

Got a problem where when I try to access https://betterexaminations.ie, I get connection refused, but when I try by the ip, it works fine, (https://) 46.137.41.29.

Any ideas what the problem could be?

I don't know how troubleshoot this. I get "503 Service Unavailable" http error for all "nginx upstreams" proxy passing calls to haproxy fast_thin and slow_thin ( server 127.0.0.1:3100 and server 127.0.0.1:3200 ), which loadbalance on 6 Thin servers ( 127.0.0.1:3000 .. 3005 ). Static files like /blog are currently fine. The falldown is: nginx on port 80 - haproxy on 3100 and 3200 - thin on 3000 ..

As far as I can see Nginx supports by default 2 log files: error_log (tracks issues related to the Nginx server itself) and access_log (tracks requests processed by Nginx).

Owncloud and chrooted nginx 9 weeks 3 days ago

ok maybe more infos needed...In nginx.conf (chroot)I get some lines like fastcgi_pass unix:/run/php-fpm/php-fpm.sock;But i've not this files in chrooted /runSo can i make use of php-fpm in chroot ?Here my nginx.conf :#user html; worker_processes 1;

#error_log logs/error.log; #error_log logs/error.log notice; #error_log logs/error.log info;

#pid logs/nginx.pid;

events { wo

Here's my NGINX config (no apache, just php-fpm):

user nginx; worker_processes 1; error_log /usr/local/nginx/logs/error.log notice; pid /var/run/nginx.pid;

events { worker_connections 384; }

http { include mime.types; default_type application/octet-stream; access_log off; server_tokens off; sendfile