Nginx 413 Request Entity Too LargeHow do I fix this problem and allow image upload upto 2MB in size using nginx web-server working in reverse proxy or stand-alone mode on Unix like operating systems?
-bash-3.2# php -v
PHP 4.4.9 (cli) (built: May 4 2010 13:55:07)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
with the ionCube PHP Loader v3.3.14, Copyright (c) 2002-2010, by ionCube Ltd., and with Zend Optimizer v3.3.3, Copyright (c) 1998-2007, by Zend Technologies
/usr/local/apache/logs/error_log
/usr/local/apache/logs/suphp.logHere are some common errors:
SoftException in Application.cpp:357: UID of script "/home/user/public_html/test.php" is smaller than min_uidSoftException in Application.cpp:422: Mismatch between target UID (511) and UID (510) of file "/home/user/public_html/test.php"SoftException in Application.cpp:264: File "/home/user/public_html/test.php" is writeable by others/home/user/public_html/.htaccess: Invalid command 'php_flag',
perhaps misspelled or defined by a module not included in the server
configurationallow_file_group_writeable=false
allow_file_others_writeable=false
allow_directory_group_writeable=false
allow_directory_others_writeable=false-rwsr-xr-x 1 root root 341K Mar 30 12:25 /opt/suphp/sbin/suphp*If it’s missing the ‘s’ in the permissions column, you need to re-add the sticky bit to allow users on the system to execute it properly:
chmod +s /opt/suphp/sbin/suphp
--- mod_rpaf-2.0.c.org 2012-05-17 12:05:34.082130109 +0900 +++ mod_rpaf-2.0.c 2012-05-17 12:16:41.648138252 +0900 @@ -147,8 +147,8 @@ static apr_status_t rpaf_cleanup(void *data) { rpaf_cleanup_rec *rcr = (rpaf_cleanup_rec *)data; - rcr->r->connection->remote_ip = apr_pstrdup(rcr->r->connection->pool, rcr->old_ip); - rcr->r->connection->remote_addr->sa.sin.sin_addr.s_addr = apr_inet_addr(rcr->r->connection->remote_ip); + rcr->r->connection->client_ip = apr_pstrdup(rcr->r->connection->pool, rcr->old_ip); + rcr->r->connection->client_addr->sa.sin.sin_addr.s_addr = apr_inet_addr(rcr->r->connection->client_ip); return APR_SUCCESS; } @@ -161,7 +161,7 @@ if (!cfg->enable) return DECLINED; - if (is_in_array(r->connection->remote_ip, cfg->proxy_ips) == 1) { + if (is_in_array(r->connection->client_ip, cfg->proxy_ips) == 1) { /* check if cfg->headername is set and if it is use that instead of X-Forwarded-For by default */ if (cfg->headername && (fwdvalue = apr_table_get(r->headers_in, cfg->headername))) { @@ -180,11 +180,11 @@ if (*fwdvalue != '\0') ++fwdvalue; } - rcr->old_ip = apr_pstrdup(r->connection->pool, r->connection->remote_ip); + rcr->old_ip = apr_pstrdup(r->connection->pool, r->connection->client_ip); rcr->r = r; apr_pool_cleanup_register(r->pool, (void *)rcr, rpaf_cleanup, apr_pool_cleanup_null); - r->connection->remote_ip = apr_pstrdup(r->connection->pool, ((char **)arr->elts)[((arr->nelts)-1)]); - r->connection->remote_addr->sa.sin.sin_addr.s_addr = apr_inet_addr(r->connection->remote_ip); + r->connection->client_ip = apr_pstrdup(r->connection->pool, ((char **)arr->elts)[((arr->nelts)-1)]); + r->connection->client_addr->sa.sin.sin_addr.s_addr = apr_inet_addr(r->connection->client_ip); if (cfg->sethostname) { const char *hostvalue; if (hostvalue = apr_table_get(r->headers_in, "X-Forwarded-Host")) {
patch -p1 < patch_mod_rpaf
$> git clone http://github.com/pagespeed/cpanel.git /var/cpanel/easy/apache/custom_opt_mods/Cpanel/
$> cd /var/cpanel/easy/apache/custom_opt_mods/Cpanel/Easy && tar -zcvf Speed.pm.tar.gz pagespeed
/scripts/easyapache). Rebuild the Apache server, reboot it, and you’re good to go!Hotlinking is a term used on the Internet that refers to the practice of displaying an image on a website by linking to the same image on another website, rather than saving a copy of it on the website on which the image will be shown.Hotlinking can be major issue for bandwidth leeching for some sites. Here is small config part which you can add to prevent those activities.
server {
location ~ \.(mp4|mp3|wav|avi)$ {
valid_referers blocked example.com *.example.com;
if ($invalid_referer) {
return 403;
}
}
}wget http://www.codestance.com/somefile.tar
--2013-07-03 16:04:14-- http://www.codestance.com/somefile.tar
Resolving www.codestance.com... 93.139.143.110
Connecting to www.codestance.com|93.139.143.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 46397440 (44M) [text/plain]
Saving to: "somefile.tar"
100%[======================================================================>] 46,397,440 273M/s in 0.2s
2013-07-03 16:04:14 (273 MB/s) - "somefile.tar"93.139.143.110 - - [03/Jul/2013:16:04:14 +0000] "GET /somefile.tar HTTP/1.1" 200 46397440 "-" "Wget/1.12 (linux-gnu)" "-"location /download {
post_action /adcounter;
}
location /adcounter{
proxy_pass http://www.codestance.com/api/v1/adcounter?FileName=$request&ClientIP=$remote_addr& bytes_sent=$body_bytes_sent&status=$request_completion¶ms=$args;
internal;
}wget http://www.codestance.com/somefile.tar
--2013-07-03 16:12:53-- http://www.codestance.com/somefile.tar
Resolving www.codestance.com... 93.139.143.110
Connecting to www.codestance.com|93.139.143.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 46397440 (44M) [text/plain]
Saving to: "somefile.tar"
100%[======================================================================>] 46,397,440 298M/s in 0.2s
2013-07-03 16:12:53 (298 MB/s) - "somefile.tar"93.139.143.110 - - [03/Jul/2013:16:12:53 +0000] "GET /api/v1/adcounter?FileName=GET /somefile.tar HTTP/1.1&ClientIP=93.139.143.110&bytes_sent=46397440&status=OK¶ms= HTTP/1.0" 200 10 "-" "Wget/1.12 (linux-gnu)"93.139.143.110 - - [03/Jul/2013:16:18:01 +0000] "GET /api/v1/adcounter?FileName=GET /somefile.tar HTTP/1.1&ClientIP=93.139.143.110&bytes_sent=27838464&status=¶ms= HTTP/1.0" 200 10 "-" "Wget/1.12 (linux-gnu)"
sudo apt-get update
sudo apt-get install php5-fpm
# check if everything is working
php5-fpm -vsudo apt-get install php5-common
sudo apt-get install php5-curl
sudo apt-get install php5-mysqli
...sudo nano /etc/php5/fpm/pool.d/www.conf# pool name
[www1]
# user of FPM processess
user = www-data
# group of FPM processess
group = www-data
# address on which FastCGI requests are accepted, this can also be unix socket. Mandatory for each pool
# please take in mind that they say that unix socket is bit faster than tcp but honestly i didn't notice it, what i noticed is that on unix socket i get bunch of errors..
listen = "127.0.0.1:9000"
# how process manager controll number of children. Option is mandatory
# static - child processes are fixed - pm.max_children
# ondemand - processes spawn on demand, opposite to dynamic where started processes on service started
# dynamic - processes are spawned as said depending on directives : max_children, start_servers, min_spare_servers, max_spare_servers
pm = dynamic
pm.max_children = 4096
pm.start_servers = 20
pm.min_spare_servers = 5
pm.max_spare_servers = 128
# number of requests each child should execute before respawning.
pm.max_requests = 1024
# uri on which you can check your fpm status
pm.status_path = /php-status
# log file for slow requests
slowlog = /var/log/php-fpm.slow.log
listen.backlog = -1[www1]
user = www-data
group = www-data
listen = "127.0.0.1:9000"
pm = dynamic
pm.max_children = 4096
pm.start_servers = 20
pm.min_spare_servers = 5
pm.max_spare_servers = 128
pm.max_requests = 1024
pm.status_path = /php-status
slowlog = /var/log/php-fpm.slow.log
listen.backlog = -1
[www2]
user = www-data
group = www-data
listen = "127.0.0.1:9001"
pm = dynamic
pm.max_children = 4096
pm.start_servers = 20
pm.min_spare_servers = 5
pm.max_spare_servers = 128
pm.max_requests = 1024
pm.status_path = /php-status
slowlog = /var/log/php-fpm.slow.log
listen.backlog = -1
[www3]
user = www-data
group = www-data
listen = "127.0.0.1:9002"
pm = dynamic
pm.max_children = 4096
pm.start_servers = 20
pm.min_spare_servers = 5
pm.max_spare_servers = 128
pm.max_requests = 1024
pm.status_path = /php-status
slowlog = /var/log/php-fpm.slow.log
listen.backlog = -1
[www4]
user = www-data
group = www-data
listen = "127.0.0.1:9003"
pm = dynamic
pm.max_children = 4096
pm.start_servers = 20
pm.min_spare_servers = 5
pm.max_spare_servers = 128
pm.max_requests = 1024
pm.status_path = /php-status
slowlog = /var/log/php-fpm.slow.log
listen.backlog = -1upstream php {
server 127.0.0.1:9100;
server 127.0.0.1:9001;
server 127.0.0.1:9002;
server 127.0.0.1:9003;
}location ~ \.php$ {
fastcgi_pass php;
}server {
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Real-Host $host;
proxy_read_timeout 120;
}
}
apc.enabled = 1
apc.shm_segments = 1
apc.shm_size = 128M
apc.optimization = 0
apc.num_files_hint = 512
apc.user_entries_hint = 1024
apc.ttl = 0
apc.user_ttl = 0
apc.gc_ttl = 600
apc.cache_by_default = 0
apc.slam_defense = 0
apc.use_request_time = 1
apc.mmap_file_mask = /tmp/apc-accountname.XXXXXX
;OR apc.mmap_file_mask = /dev/zero
apc.file_update_protection = 2
apc.enable_cli = 0
apc.max_file_size = 8M
apc.stat = 1
apc.write_lock = 1
apc.report_autofilter = 0
apc.include_once_override = 0
apc.rfc1867 = 0
apc.rfc1867_prefix = "upload_"
apc.rfc1867_name = "APC_UPLOAD_PROGRESS"
apc.rfc1867_freq = 0
apc.localcache = 1
apc.localcache.size = 512
apc.coredump_unmap = 0
apc.stat_ctime = 0apt-get install nginx# you must set worker processes based on your CPU cores, nginx does not benefit from setting more than that
worker_processes = auto; #some last versions calculate it automatically, thanks to Diego :)
# number of file descriptors used for nginx
# the limit for the maximum FDs on the server is usually set by the OS.
# if you don't set FD's then OS settings will be used which is by default 2000
worker_rlimit_nofile 100000;
# only log critical errors
error_log /var/log/nginx/error.log crit
# provides the configuration file context in which the directives that affect connection processing are specified.
events {
# determines how much clients will be served per worker
# max clients = worker_connections * worker_processes
# max clients is also limited by the number of socket connections available on the system (~64k)
worker_connections 4000;
# optmized to serve many clients with each thread, essential for linux
use epoll;
# accept as many connections as possible, may flood worker connections if set too low
multi_accept on;
}
# cache informations about FDs, frequently accessed files
# can boost performance, but you need to test those values
open_file_cache max=200000 inactive=20s;
open_file_cache_valid 30s;
open_file_cache_min_uses 2;
open_file_cache_errors on;
# to boost IO on HDD we can disable access logs
access_log off;
# copies data between one FD and other from within the kernel
# faster then read() + write()
sendfile on;
# send headers in one peace, its better then sending them one by one
tcp_nopush on;
# don't buffer data sent, good for small data bursts in real time
tcp_nodelay on;
# server will close connection after this time
keepalive_timeout 30;
# number of requests client can make over keep-alive -- for testing
keepalive_requests 100000;
# allow the server to close connection on non responding client, this will free up memory
reset_timedout_connection on;
# request timed out -- default 60
client_body_timeout 10;
# if client stop responding, free up memory -- default 60
send_timeout 2;
# reduce the data that needs to be sent over network
gzip on;
gzip_min_length 10240;
gzip_proxied expired no-cache no-store private auth;
gzip_types text/plain text/css text/xml text/javascript application/x-javascript application/xml;
gzip_disable "MSIE [1-6]\.";
/etc/init.d/nginx start|restart/etc/init.d/nginx configtestserver_tokens off;
# limit the number of connections per single IP
limit_conn_zone $binary_remote_addr zone=conn_limit_per_ip:10m;
# limit the number of requests for a given session
limit_req_zone $binary_remote_addr zone=req_limit_per_ip:10m rate=5r/s;
# zone which we want to limit by upper values, we want limit whole server
server {
limit_conn conn_limit_per_ip 10;
limit_req zone=req_limit_per_ip burst=10 nodelay;
}
# if the request body size is more than the buffer size, then the entire (or partial) request body is written into a temporary file
client_body_buffer_size 128k;
# headerbuffer size for the request header from client, its set for testing purpose
client_header_buffer_size 3m;
# maximum number and size of buffers for large headers to read from client request
large_client_header_buffers 4 256k;
# read timeout for the request body from client, its set for testing purpose
client_body_timeout 3m;
# how long to wait for the client to send a request header, its set for testing purpose
client_header_timeout 3m;/etc/init.d/nginx configtest/etc/init.d/nginx restart|reload