Custom Query (2296 matches)

I've got an nginx server which stops working around once a week with this error. Restarting nginx cures it. Any suggestions?

I've got OS configuration set to allow many file handles. Here's the config:

user www-data; worker_processes 10; worker_rlimit_nofile 50000;

pid /var/run/nginx.pid;

events {

worker_connections 30000; multi_accept on;

}

http {

## # Basic Settings ##

sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; types_hash_max_size 2048;

# server_tokens off;

push_stream_shared_memory_size 100M;

client_max_body_size 10m; client_body_buffer_size 16k;

server_names_hash_bucket_size 64;

This is error.log from nginx. I setup nginx with rtmp server. And using record command to record and stored in my specific directory. And I want to access straight direct the video file in web browser. I got 400 Bad Request.

2015/02/06 17:14:40 [info] 2789#0: *1 client sent invalid request while reading client request line, client: XX.XXX.XX.XX, server: localhost, request: "GET /vod/YwlMkR5RQHLJL23ifhkKDXxSSrYE5CoFqfwj7y-2015-02-06%H59.flv HTTP/1.1"
2015/02/06 17:14:50 [info] 2789#0: *3 client closed connection while waiting for request, client: XX.XXX.X.XX, server: 0.0.0.0:80
2015/02/06 17:14:50 [info] 2789#0: *2 client closed connection while waiting for request, client: XX.XXX.X.XX, server: 0.0.0.0:80

My /usr/local/nginx/conf/nginx.conf

#user  nobody;
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 {
    worker_connections  1024;
}

http {
    ignore_invalid_headers off;
     #proxy_buffering off;
    include       mime.types;
    default_type  application/octet-stream;
    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;
    server {
        listen       80;
        server_name  localhost;
        ignore_invalid_headers off;
        #charset koi8-r;

        #access_log  logs/host.access.log  main;
        error_log    /var/log/nginx/error.log debug;
       error_log logs/error.log debug;

        location / {
            root   html;
            index  index.html index.htm;
        }

        location /vod {
            alias /var/rec;
        }
rtmp {
        server {
                listen 1935;
                chunk_size 4096;
                notify_method get;
                allow publish my_ip;
                deny publish all;

                allow play my_ip;
                deny play all;

                application  live{
                        live on;
                        record all;
                        record_path /var/rec;
                }
                
                application live2 {
                        live on;
                        record all manual;
                        record_suffix -%Y-%m-%d%-%H%M.flv;
                        record_path /var/rec;
                }

                application vod {
                        #play /var/rec;
                        play http://54.169.145.234/vod/;
                }

               location /control {
          #  add_header Access-Control-Allow-Headers Origin,X-Requested-With,Content-Type,Accept;   
          #  add_header Access-Control-Allow-Origin *;
             rtmp_control all;
        }
        #error_page  404              /404.html;

        # redirect server error pages to the static page /50x.html
        #
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }



        }
}

Hi Support,

our website uses client side certs and while accessing the website on microsoft edge, we get "400 Bad Request No required SSL certificate was sent" frequently. The NGINX Version is nginx/1.10.1 and below is the code from NGINX. The website can be accessed on chrome, firefox without any issues.

server {

listen 10.70.10.108:443; server_name g1.xyz.com;

access_log /var/log/nginx/g1_xyz_access.log;

ssl on; ssl_certificate /etc/nginx/s1_xyz_com.crt; ssl_certificate_key /etc/nginx/s1_xyz.com.key; ssl_client_certificate /etc/nginx/main.crt; ssl_dhparam /etc/nginx/dhparams.pem; ssl_crl /etc/CA/crl/crldb.pem; ssl_verify_client on; ssl_verify_depth 1; client_max_body_size 200M;

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:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';

ssl_prefer_server_ciphers on; keepalive_timeout 300;

ssl_session_cache shared:SSL:10m; ssl_session_timeout 10m;

charset utf-8;

location / {

proxy_pass ​http://10.70.10.221; proxy_connect_timeout 1800;

proxy_send_timeout 1800; proxy_read_timeout 1800; send_timeout 1800; proxy_redirect off; proxy_buffering off; proxy_set_header Host $host; proxy_set_header URI $uri;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

}

}

Regards, Rupesh...