Here is the suggestion: Basically, default nginx fastcgi params is available in /etc/nginx/fastcgi_params and one would only need to add "include /etc/nginx/fastcgi_params;" in ISPConfig apps nginx vhost file to use them, without typing them all again and again. The following is the default in Ubuntu Noble: Code: fastcgi_param QUERY_STRING $query_string; fastcgi_param REQUEST_METHOD $request_method; fastcgi_param CONTENT_TYPE $content_type; fastcgi_param CONTENT_LENGTH $content_length; fastcgi_param SCRIPT_NAME $fastcgi_script_name; fastcgi_param REQUEST_URI $request_uri; fastcgi_param DOCUMENT_URI $document_uri; fastcgi_param DOCUMENT_ROOT $document_root; fastcgi_param SERVER_PROTOCOL $server_protocol; fastcgi_param REQUEST_SCHEME $scheme; fastcgi_param HTTPS $https if_not_empty; fastcgi_param GATEWAY_INTERFACE CGI/1.1; fastcgi_param SERVER_SOFTWARE nginx/$nginx_version; fastcgi_param REMOTE_ADDR $remote_addr; fastcgi_param REMOTE_PORT $remote_port; fastcgi_param REMOTE_USER $remote_user; fastcgi_param SERVER_ADDR $server_addr; fastcgi_param SERVER_PORT $server_port; fastcgi_param SERVER_NAME $server_name; # PHP only, required if PHP was built with --enable-force-cgi-redirect fastcgi_param REDIRECT_STATUS 200; This default has already included remote user param, which one may want to consider disabling it depending if it is considered unsafe. The other is its https param will want https only if it is not empty, while in apps vhost file it will always require htpps. So these two params, may be modified. I believe any additional fastcgi params that already in used in apps vhost file can be maintained right after it.
