https://en.wikipedia.org/wiki/Time_and_materials
https://en.wikipedia.org/wiki/Agile_software_development
You should analyze blocked URLs and should understand why some resources are not processed by nginx, and why they are proxied to apache instead.
Perhaps you should hire a system administrator.
access_log off; and show the nginx log with 503 errors.
location ~ \.php$ {limit_conn perip 1;}location @fallback {limit_conn perip 1;proxy_pass http://127.0.0.1:8080;proxy_redirect http://127.0.0.1:8080 /;proxy_set_header Host $host;proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;proxy_set_header X-Forwarded-Proto $scheme;access_log off;}
You've configured your Ngix wrong. Show your configuration.
почему то 😂
Yes, you can limit static resources too, but it's practically useless. Nginx works effectively.
Yes, It will. But html files are the static resource and they will not load your CPU in contrast of php scripts.
Note that I've show only an example. Your nginx location structure may differs.
limit_conn_zone $binary_remote_addr zone=backend:10m; location ~ \.php$ { limit_conn backend 1; ... }
10 is good. Browsers do not make more than 6 parallel requests in total (including all static resources).
You can limit this value even to 1 per single IP, in backend location, however.
