Add client_max_body_size Now that you are editing the file you need to add the line into the server block, like so; server { client_max_body_size 8M; //other lines… } If you are hosting multiple sites add it to the http context like so; http { client_max_body_size 8M; //other lines… } And also update the upload_max_filesize in … Read more
This is most likely happening because of the long domain name. You can fix this by adding server_names_hash_bucket_size 64; at the top of your http block (probably located in /etc/nginx/nginx.conf). I quote from the nginx documentation what to do when this error appears: In this case, the directive value should be increased to the next … Read more
I think this will do it for you: location / { try_files /base.html =404; }
That is not an nginx configuration file. It is part of an nginx configuration file. The nginx configuration file (usually called nginx.conf) will look like: events { … } http { … server { … } } The server block is enclosed within an http block. Often the configuration is distributed across multiple files, by … Read more
Running nginx -t through your commandline will issue out a test and append the output with the filepath to the configuration file (with either an error or success message).
To expand on Charles Duffy’s answer, Nginx uses the daemon off directive to run in the foreground. If it’s inconvenient to put this in the configuration file, we can specify it directly on the command line. This makes it easy to run in debug mode (foreground) and directly switch to running in production mode (background) … Read more
replace include fastcgi_params; with include fastcgi.conf; and remove fastcgi_param SCRIPT_FILENAME … in nginx.conf
If you can use a static IP then just use that, it’ll startup and just return 503‘s if it doesn’t respond. Use the resolver directive to point to something that can resolve the host, regardless if it’s currently up or not. Resolve it at the location level, if you can’t do the above (this will … Read more
There are two methods you can take for this. Unfortunately some work for some EB application types and some work for others. Supported/recommended in AWS documentation For some application types, like Java SE, Go, Node.js, and maybe Ruby (it’s not documented for Ruby, but all the other Nginx platforms seem to support this), Elasticbeanstalk has … Read more
Just to note that nginx has now support for Websockets on the release 1.3.13. Example of use: location /websocket/ { proxy_pass ​http://backend_host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection “upgrade”; proxy_read_timeout 86400; } You can also check the nginx changelog and the WebSocket proxying documentation.